-
Notifications
You must be signed in to change notification settings - Fork 6
Guard file uploads with remote object preconditions #119
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
AysajanE
wants to merge
4
commits into
8thpark:main
Choose a base branch
from
AysajanE:northset/m-1056
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.
+266
−41
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
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
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.
kind:"done"path has no test coverageThe branch where
remoteHash !== expected.hashbutremoteHash === hashBytes(bytes)— meaning the remote already holds our bytes from a previous orphaned upload — returns{ ok: true, kind: "done" }and marks the action ascompleted. This is the "safely recognize identical orphaned uploads during retries" feature called out in the PR summary. It is not exercised by any test: the new #110 test only exercises theremoteMatchesfallback after a failed conditional PUT, not this pre-PUT short-circuit. A targeted test (second-pass retry where the prior pass uploaded the file but lost the manifest CAS) would pin this behaviour against future refactors.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.
@AysajanE Could you address this comment please?
Uh oh!
There was an error while loading. Please reload this page.
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.
Addressed in
87fae77. The retry test now makes this exact pre-PUT path explicit: the first pass uploadsa.mdand loses the manifest CAS; the second pass sees the ancestor manifest plus the already-uploaded matching bytes, adopts them, and leavesfilePutsat 1. It also deep-asserts the complete successful retry outcome.npm test && npm run lint && npm run buildpasses (139 tests).