-
Notifications
You must be signed in to change notification settings - Fork 715
fix: add partial response warning #4658
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
WalkthroughThe Changes
Possibly related PRs
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (1)
- src/handler/http/request/search/multi_streams.rs (4 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
src/handler/http/request/search/multi_streams.rs (1)
Pattern
**/*.rs: You are a smart rustlang pull request reviewer.
You are going to review all the rustlang files.
Be concise, and add a brief explanation to your suggestionsMake sure the responses are not too verbose and keep the suggestions to the point i.e. actionable.
🔇 Additional comments (3)
src/handler/http/request/search/multi_streams.rs (3)
168-168: LGTM!The declaration of
range_erroris clear and correctly initialized.
202-218: LGTM!The logic for enforcing the maximum query range per stream settings is correctly implemented. It adjusts the
start_timewhen the query duration exceeds themax_query_rangeand accumulates a range error message.
382-390: LGTM!The code appropriately updates
multi_resto indicate when the response is based on partial data by settingis_partialtotrueand adjustingfunction_error.
Summary by CodeRabbit
New Features
Bug Fixes