The Rust wire format for CreateUser always includes permissions_len:u32_le on the wire, even when has_permissions=0. The server-side decoder unconditionally reads these 4 bytes (see create_user.rs#L82-L83), and the Rust encoder always writes them (see create_user.rs#L61-L62).
In the Go SDK (foreign/go/internal/command/user.go), the nil-permissions branch only writes has_permissions=0 (1 byte) and skips the 4-byte permissions_len=0:
} else {
bytes[position] = byte(0) // writes flag only, no permissions_len
}
The server will try to read 4 bytes that aren't there, causing a parse failure or reading into the next message.
Fix: Write permissions_len=0 (4 zero bytes) after the flag in the else branch, and add 4 to the base capacity.
The Rust wire format for
CreateUseralways includespermissions_len:u32_leon the wire, even whenhas_permissions=0. The server-side decoder unconditionally reads these 4 bytes (see create_user.rs#L82-L83), and the Rust encoder always writes them (see create_user.rs#L61-L62).In the Go SDK (
foreign/go/internal/command/user.go), the nil-permissions branch only writeshas_permissions=0(1 byte) and skips the 4-bytepermissions_len=0:The server will try to read 4 bytes that aren't there, causing a parse failure or reading into the next message.
Fix: Write permissions_len=0 (4 zero bytes) after the flag in the else branch, and add 4 to the base capacity.