Repository navigation
test(live): assert the Disk facts a two-way sync builds on - #13
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The probes showed on the test account: the Disk's sha256 is the content's, a replacing upload keeps the resource_id, the Disk revision moves with each write, and a delete with a wrong md5 is refused with 409. Yandex's docs leave all four open; the sync design relies on them, so the release check now asserts them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Two-way folder sync (next feature) needs four facts that Yandex's API docs leave open. Probed on the test account on 2026-11-18:
sha256equals the sha256 of the file's content;overwrite=truekeeps the file'sresource_id;revision(GET /v1/disk) moves with each write, so a watch can poll it before listing;DELETE ?md5=<wrong>is refused with 409 and the file stays.The live check now asserts them, so a change at Yandex fails the release check instead of the sync.
Also:
bin/liveskips the check when the version already has a record, so #12'sfolders browsestep had not run against the Disk. It ran in this PR's live check and passed.🤖 Generated with Claude Code
Conformance
0.2.0 9004287f2fdc84b3524652352915d5cb6382955a 2026-11-18 scripts/live.sh v2:00ba1ad80aabdce948b0c64f2a6a29a54ca74e78c356462c78ade3240570392a