Skip to content

fix(q): distinguish decode failures from Q errors - #16

Closed
belowzeroff wants to merge 2 commits into
RayforceDB:masterfrom
belowzeroff:fix/q-decode-error-status
Closed

belowzeroff wants to merge 2 commits into
RayforceDB:masterfrom
belowzeroff:fix/q-decode-error-status

Conversation

@belowzeroff

@belowzeroff belowzeroff commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • return RAY_ERROR for valid Q error frames from q_decode
  • keep malformed or unsupported wire payloads returning NULL with diagnostic text
  • add regression coverage for Q error decoding behavior

Testing

  • git diff --check
  • codec selftest against local static Rayforce library

Notes

This branch is stacked on top of fix/q-codec-transport-safety / #15, because GitHub does not allow targeting a fork-only base branch in the upstream repository. Until #15 lands, this PR shows both commits.

@protocolstardust

Copy link
Copy Markdown
Collaborator

Closing as superseded: #15 and #17–#21 landed on master via #21 (and #14 via its own merge), and #17 deliberately reverted the one change this PR still carries over master — returning NULL for a malformed decode instead of the core's error object. master keeps the #17 behaviour, so there is nothing left here to merge. Thanks for the series.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants