Add test for NothingToQuery when buffer budget exhausted - #1340
Merged
Conversation
Assert getNextQuery returns NothingToQuery for a zero and negative budget, locking in the `budget <= 0` early return directly. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KcQaeMwie245tF3aa5Jkwk
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughA new Vitest unit test is added to FetchState Budget Exhaustion Test
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
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.
Summary
Add a test case to verify that
FetchState.getNextQueryreturnsNothingToQuerywhen the buffer budget is exhausted or non-positive.Changes
FetchState_test.resNothingToQuerybeing returnedDetails
The test documents the expected behavior that a non-positive budget is the only reason
getNextQuerywould returnNothingToQueryfor an initial fetch state, ensuring the shared buffer pool constraints are properly enforced.https://claude.ai/code/session_01KcQaeMwie245tF3aa5Jkwk
Summary by CodeRabbit