Use sas token from recently queried v2 checkpoint incase the one we currently have is expired (backport #7579) [release/4.10.x] #7580
Conversation
This file contains 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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
mergify
bot
requested review from
markschlosseratbentley,
ben-polinsky and
saeeedtorabi
nick4598
approved these changes
Jan 21, 2025
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.
I believe fixes bug where:
1)Backend opens v2 checkpoint
2)Backend closes v2 checkpoint
3)time passes and token on that container expires
4) Backend opens v2 checkpoint on same container, gets 403 trying to get new manfiest because it uses the old token. Resulting in BE_SQLITE_CANTOPEN for newer checkpoints.
This is an automatic backport of pull request #7579 done by [Mergify](https://mergify.com).