Skip to content

node-sdk: deserializeVoidResponse now ignores payload length for all void commands #3128

@atharvalade

Description

@atharvalade

Problem

deserializeVoidResponse was changed from:

  • status === 0 && data.length === 0
    to:
  • status === 0

This applies to all void commands, not just SendMessages.

Why this is critical

This removes a useful protocol safety check.
Malformed or unexpected payloads for void commands are now silently accepted.

Where

  • foreign/node/src/client/client.utils.ts

Expected

Keep strict empty-payload validation for true void commands.
Handle SendMessages with a dedicated response deserializer instead of weakening global void validation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions