Reorder RTO5f to check for unsupported object type before pool lookup#428
Merged
lawrence-forooghian merged 1 commit intomainfrom Feb 25, 2026
Merged
Reorder RTO5f to check for unsupported object type before pool lookup#428lawrence-forooghian merged 1 commit intomainfrom
lawrence-forooghian merged 1 commit intomainfrom
Conversation
We can safely delete RTO5f2c from the spec entirely as there were no live SDK implementations that relied on it
VeskeR
force-pushed
the
RTO5f-error-handling
branch
from
3b7435b to
9f4d7de
Compare
lawrence-forooghian
approved these changes
Feb 25, 2026
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
2 participants
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.
Makes more sense to check for supported object types before actually adding them to the pool in RTO5f1