mirror of
https://github.com/SignTools/SignTools.git
synced 2026-04-30 20:35:49 +03:00
[GH-ISSUE #644] Edge case: SignTools times out before CI finishes when developer account is unusually slow #122
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/SignTools#122
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @jluo98 on GitHub (Feb 21, 2026).
Original GitHub issue: https://github.com/SignTools/SignTools/issues/644
!! Please fill in this template, DO NOT ignore or delete it. !!
I tried basic troubleshooting first
Describe the bug
SignTools has a built-in timeout that's not tied to the result of a running CI job.
When the CI job runs longer than the default timeout (developer account, contacting Apple server, not actually failing), even when the run was successful, the upload would fail with an 404 error.
To reproduce
Steps to reproduce the behavior:
Expected behavior
SignTools waits for the CI to run instead of timing out early.
Logs
If possible, please include logs.
SignTools: https://pastebin.com/A4PdpccG
SignTools-CI: https://pastebin.com/meHceWic
Screenshots
N/A
System configuration
Additional context
N/A
@jluo98 commented on GitHub (Feb 21, 2026):
The log I attached came from the latest run. This run actually ended with a cancelled CI instead of a failed upload.
@jluo98 commented on GitHub (Feb 22, 2026):
Did another test. Using Github Actions is taking over 30 minutes and the run gets cancelled before it finishes. Using a self-hosted Mac, the job finishes within minutes, completely normally. Github's machines seem to have some kind of throttling problem reaching Apple's servers.
Again, I'd consider this an edge case, a fix is not necessary, but nontheless beneficial.
@ViRb3 commented on GitHub (Feb 22, 2026):
Yes, there are hardcoded unconditional timeouts:
These are there because sometimes things can stall forever, and you don't want to burn credits or even money endlessly. If you want, you can change those as you please on your personal SignTools-CI copy. In my personal experience, nothing has ever taken close to 30 mins, unless there's an underlying problem which should be addressed instead.
@jluo98 commented on GitHub (Feb 22, 2026):
@ViRb3 yes the 30 minute timeout makes total sense for CI runs and shouldn’t be changed.
But on the SignTools side, it times out (turns red) way before that, I believe around 15 minutes.
One of my runs took around 20 minutes to complete, but by then SignTools already closed the upload path so the job failed with a 404 error. I’m referring to this situation.
Edit: but you’re absolutely right. A run shouldn’t take this long anyway. GitHub’s machines probably had some problems yesterday/recently that if using a developer account, it’s taking absolutely forever to get all the entitlements from Apple.
@ViRb3 commented on GitHub (Feb 23, 2026):
The client-side timeout can also be set freely, via the SignTools yml config:
github.com/SignTools/SignTools@4efbeea62c/src/config/config.go (L84)It's set to 30, matching SignTools-CI.
@jluo98 commented on GitHub (Feb 23, 2026):
Oh you're right, I had mine set to 15 a long time ago and forgot about it. Thanks for pointing that out! I'll close this issue now.