Repository navigation
Release v1.1.0 (ADR-0037) - #2
Merged
Merged
Conversation
Poison bodies are dead-lettered as a PoisonRecord instead of being forwarded raw, a null-body TextMessage is treated as poison, and unsupported schema versions follow broker-bindings 5.7. Pin conformance v1.8.0 and run version_gate_artemis.
BytesMessage bodies were truncated on read. The consumer now reads every byte and resets the message before a handler sees it; a body that is not valid UTF-8 goes to <queue>.dlq as an ADR-0035 record with raw_encoding base64.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Poison-record and Pulsar version-gate parity per ADR-0037 (conformance v1.8.0). See CHANGELOG.md for the full list; the envelope stays at schema_version 1.