-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Fix LRO poller to treat HTTP 404/406 as transient during transaction-status polling #46310
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
Open
Copilot
wants to merge
4
commits into
main
Choose a base branch
from
copilot/fix-lro-poller-transaction-status
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+394
−2
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
e05b180
Fix LRO poller to treat HTTP 404 and 406 as transient during transact…
Copilot 304414a
Restore original 404 retry logic (with counter) and add separate 406 …
Copilot 2cd34a0
Merge branch 'main' into copilot/fix-lro-poller-transaction-status
PallabPaul 00bad60
Merge branch 'main' into copilot/fix-lro-poller-transaction-status
PallabPaul 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
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
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.
The code enforces the 404 retry limit using a monotonic
_not_found_count, but the tests/docstrings describe the behavior as '3 consecutive 404s'. As implemented, non-consecutive 404s (e.g., 404 → 406 → 404 → 406 → 404) will still eventually hit the limit and fail. Please either (a) reset_not_found_countafter any successful poll / any non-404 attempt (including the 406 transient path) to make it truly 'consecutive', or (b) update the docstrings/tests to explicitly state the limit is on the total number of 404s during a polling run.