feat(jetstream): handle "no results" status in direct APIs #336
Conversation
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
…levant tests - Added `isNoResults` method to identify "no results" error in JetStream errors. - Updated logic in `jsm_direct.ts` to stop iterators on "no results" status. - Enhanced tests with scenarios for handling batches and direct message retrieval when no messages are available. Signed-off-by: Alberto Ricart <[email protected]>
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.
Previously, an error was thrown, but this is inconsistent on how the client handles this conditions for fetch and other similar user-initiated operations.
isNoResultsmethod to identify "no results" error in JetStream errors.jsm_direct.tsto stop iterators on "no results" status.Fix #335