a6ba6e6583
The schema fix to use uint32 for status was the right call, but the error persists. The fact that the raw bytes are being printed means the new code IS running, but the error must be coming from somewhere outside the inline try/catch blocks. Wrapping the whole connect() in a safety net so we'll see a stack trace on the next run and can pinpoint the exact line.