fix(delivery): allow large release assets to finish processing #50
No reviewers
Labels
No labels
app-migration
bug
ci-cd
cluster
Documentation
duplicate
enhancement
gpu
invalid
networking
question
security
Storage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/workflows!50
Loading…
Reference in a new issue
No description provided.
Delete branch "kiyi/release-upload-timeout"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ComfyUI run 141 sent the release asset body, then the uploader timed out waiting for the HTTP response. HTTPSConnection used a 300-second timeout even though the owner’s NPM read timeout is 1800 seconds.
Keep the existing 300-second connection/send timeout and switch the connected socket to a 1800-second read timeout after sending the full multipart body. Log the transition to waiting for Forgejo, and close the connection on both success and failure. HTTP errors still block publication; no automatic POST retry is added because a timed-out request may already have created the asset. The overall job deadline remains unchanged.
Validation: 168 Linux regression tests pass, including upload success, HTTP rejection and response timeout, multipart size/content, timeout ordering, one POST and connection cleanup. git diff --check passes. Rebound one existing self-scan exception only because the health-check call moved lines; its scope/expiry are unchanged. Added proxy/Forgejo log locations to the delivery guide.
This corrects the client’s premature timeout; it does not establish why Forgejo/proxy processing takes longer than five minutes. A full-size live release upload remains to be verified after releasing and adopting this fix. Related: Homelab/Comfy-UI#1 and #5.