Repository navigation
review: fix/updater-image-behind-proxy #36
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
Closed
Closed
Changes from all commits
Commits
Show all changes
3 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
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.
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.
Script executed:
Repository: geiresx/CashPilot
Length of output: 13143
Script executed:
Repository: geiresx/CashPilot
Length of output: 27893
Script executed:
Repository: geiresx/CashPilot
Length of output: 23693
Script executed:
Repository: geiresx/CashPilot
Length of output: 9699
Script executed:
Repository: geiresx/CashPilot
Length of output: 7697
Bound stalled updater image pulls.
If Docker stalls during this pull, the worker thread can remain blocked indefinitely. After the UI returns 504, the pull can resume and launch the helper later. Add a stall timeout that still allows slow pulls making progress.
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.
A stalled pull is already bounded: the worker's client comes from docker.from_env(), whose 60 s read timeout ends a pull that sends nothing for that long, while a slow pull that keeps sending progress goes on. What was missing was the handling: a read timeout is a requests exception, not an APIError, so it would have surfaced as a 500. It now reports as an outage and starts nothing (test_a_pull_that_stalls_is_an_outage_and_starts_nothing). A pull that keeps progressing past the UI's 120 s wait can still start the helper after the UI has answered 504. That was already true before this change, because containers.run pulled the image by itself, so it is out of scope here. The optional point is done too: a proxy refusal on the image check is now raised as the proxy's reason.
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.
Analysis chain
Script executed:
Length of output: 55742
@geiresxThe new test confirms that an injectedReadTimeoutis handled. It does not verify that an idle pull times out.In the locked Docker SDK 7.2.0,
images.pull()calls the low-level pull, which explicitly passestimeout=None. The client’s 60-second default therefore does not bound this pull. The stall-timeout finding remains open; please verify the timeout with an idle pull.I understand that the late start after a 504 is out of scope for this PR. Would you like a follow-up issue for that risk?
You are interacting with an AI system.