Skip to content

[bindings] map RpcError to NetworkException for Java parity #520

@fresh-borzoni

Description

@fresh-borzoni

Search before asking

  • I searched in the issues and found nothing similar.

Description

Right now, when a transport-level RPC fails (socket error, disconnect), the bindings surface it as CLIENT_ERROR_CODE = -2. That hides the fact that it's retriable.

Java does this differently - it wraps the same kind of failure into NetworkException (code 1), which is in the retriable set. So Java clients automatically retry, so we need to close the gap.

Willingness to contribute

  • I'm willing to submit a PR!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No fields configured for Task.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions