Skip to content

fix(q): reject invalid compressed flags - #20

Merged
protocolstardust merged 6 commits into
RayforceDB:masterfrom
belowzeroff:fix/q-reject-invalid-compressed-flag
Oct 12, 2026
Merged

protocolstardust merged 6 commits into
RayforceDB:masterfrom
belowzeroff:fix/q-reject-invalid-compressed-flag

Conversation

@belowzeroff

Copy link
Copy Markdown
Contributor

Summary

  • reject Q response headers whose compressed flag is not 0 or 1 on the blocking client path
  • reject malformed server frames with invalid compressed flags before body decoding
  • add regression coverage for both blocking exchange and listener handling

User-facing behavior

Malformed peers that send an invalid compressed flag now fail as protocol/framing errors instead of being treated as compressed payloads and reported later as decompression or body errors.

Testing

  • git diff --check
  • make recheck

Notes

This branch is stacked on top of the current open fix branches, because the upstream repository cannot target fork-only base branches. Until those PRs land, this PR shows the earlier stacked commits too.

@protocolstardust
protocolstardust merged commit b3d08ab into RayforceDB:master Oct 12, 2026
1 check passed
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