fix: detect cloud-storage sync via status 'c' in addition to in_cache#3
Merged
devinslick merged 1 commit intomainfrom Feb 28, 2026
Merged
Conversation
The CI job was timing out in the sync step because the API consistently
returns in_cache=False for this account type, so the condition
`bool(t.in_cache)` never became True.
The API actually signals a completed sync through two mechanisms:
- in_cache=True — explicit flag, set on some plan types
- 'c' in status — status code that appears once the seedbox has moved
the data to permanent cloud storage
The logs show status=['sd', 'c', 'i'] appears at the very first sync poll
(immediately after progress reaches 100%), confirming 'c' is the reliable
signal on this account. Both conditions are now ORed together so the
step passes as soon as either signal is present.
https://claude.ai/code/session_01E5jYKaDuJWCb7LZgyk2u6n
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
2 participants
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.
The CI job was timing out in the sync step because the API consistently
returns in_cache=False for this account type, so the condition
bool(t.in_cache)never became True.The API actually signals a completed sync through two mechanisms:
the data to permanent cloud storage
The logs show status=['sd', 'c', 'i'] appears at the very first sync poll
(immediately after progress reaches 100%), confirming 'c' is the reliable
signal on this account. Both conditions are now ORed together so the
step passes as soon as either signal is present.
https://claude.ai/code/session_01E5jYKaDuJWCb7LZgyk2u6n