fix(xqt): tolerate unknown timeline instructions - #2490
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
1 participant
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.
X/Twitter can return timeline instructions such as
TimelineRemoveEntriesthat are absent fromInstructionUnion. Previously, one unknown instruction made the entire notification response fail to decode.Configure an XQT-specific polymorphic fallback that maps unrecognized instruction types to
UnknownInstruction, allowing supported notifications and pagination cursors to continue loading. Known types retain their existing serializers; missing discriminators and malformed known instructions still fail. Unknown instructions are skipped; this does not implement their business actions.Validation:
./gradlew :social:xqt:jvmTest --offline --console=plain— all 48 tests passed, including regression coverage for mixed known/unknown instructions, unknown-only responses, malformed known instructions, and missing type discriminators.