Repository navigation
Conversation
It looks the notarisation ticket up in Apple's CloudKit, and a dropped connection there failed the arm64 job on a disk image that was fine.
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Stapler validation retries .github/workflows/acceptance-test.yml, .github/workflows/snapshot-macos.yml |
Both workflows retry validation up to three times, with 30- and 60-second waits after the first and second failures. The snapshot workflow uses a helper for the app and each DMG. Validation fails after the third unsuccessful attempt. |
Priority:
Estimated code review effort: 2 (Simple) | ~10 minutes
Change: Bug fix
Possibly related PRs
- pgadmin-org/pgadmin4#10685: Adds a nightly acceptance job that invokes the macOS acceptance workflow. Its reported arm64 failure occurred during
xcrun stapler validate, which this PR retries.
Merge Risk: 
Minimal · up to de915
-
The retry behavior is correctly implemented in both macOS workflows, with no established merge-blocking risk.
Pre-merge checks: 
4
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
The same CloudKit connection drop failed the arm64 build of a release candidate whose bundle Gatekeeper had just accepted as notarised.
|
Squashed and pushed to master as 062099a. |
xcrun stapler validatelooks the notarisation ticket up in Apple's CloudKit, and when that connection drops it fails with error 68 (NSURLErrorDomain Code=-1005 "The network connection was lost."). That has failed:snapshot-macos.yml, which skipped assembly and acceptance in release candidate 40394287449 even though Gatekeeper had just reported the bundle asaccepted, source=Notarized Developer ID, and 3 of the last 14 nightlies at the same step;Both places now make up to three attempts, 30 and 60 seconds apart, so a genuinely bad ticket still fails, just about a minute and a half later.
Summary by CodeRabbit