-
Notifications
You must be signed in to change notification settings - Fork 3.3k
feed range query fix #46506
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
Closed
Closed
feed range query fix #46506
Changes from 1 commit
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
e4c4b39
feed range query fix - initial commit
dibahlfi fd62436
addressing sdk-agent comments
dibahlfi 34ba12a
addressing pylint comments
dibahlfi f99623b
fixing sdk-agent comments
dibahlfi f4668ab
adding new utility class
dibahlfi e35c0b1
addressing comments
dibahlfi aa4b1e2
addressing comments
dibahlfi 3474442
adding scalable token strcutrue that can also work in the future for …
dibahlfi 2a4538c
missing commit
dibahlfi 9a1e9df
making in memory representation same as wire contract
dibahlfi b98cd8a
addressing PR comments
dibahlfi 4a1b709
addressing PR comments
dibahlfi 8b22307
addressing PR comments and Pylint errors
dibahlfi 7d22830
cleaning up comments
dibahlfi ff9eb03
fixing passing continuation token to child during split
dibahlfi ea50e6b
fixing bug when the client has stale cache
dibahlfi eb50d76
unifying continuation token format for full pk path
dibahlfi aebfe70
adding more tests
dibahlfi b19dbac
addressing agent comments
dibahlfi 1007da5
fixing Pylint errors
dibahlfi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🟡 Recommendation · Correctness:
_internal_response_headers_capturemay be routed through wrong parameter pathThe execution context injects the capture dict into
new_options(theoptionsparameter):But
__QueryFeedreads it fromkwargs:Whether this works depends on how the execution context's
fetch_functionforwardsnew_options. Iffetch_function(new_options)passesnew_optionsas theoptionspositional parameter (which__QueryFeedaccepts asoptions), then the capture dict is inoptions, notkwargs— andkwargs.pop(...)always returnsNone.I traced the
QueryItemsfetch_fnclosure and it does:self.__QueryFeed(path, ..., options, ..., **kwargs)whereoptionsis positional. So_internal_response_headers_captureends up inoptionsbut is read fromkwargs.If this is the case, the capture dict never reaches
__QueryFeed, and_capture_internal_headersis always a no-op — making the entire checkpoint mechanism (including the fix in Finding #1) non-functional. Please verify thefetch_fnclosure chain and confirm the capture dict actually reacheskwargs.