coilyco-flight-deck/infrastructure
2
0
Fork 0
Code Issues 118 Pull requests Projects Releases Packages Wiki Activity Actions 2

Forgejo container registry races on concurrent multi-arch blob uploads - 'unexpected EOF' / offset mismatch / package_file 23505 #552

New issue
Open
opened 2026-07-12 22:15:33 +00:00 by coilyco-ops · 0 comments
coilyco-ops commented 2026-07-12 22:15:33 +00:00
Member
Copy link

aos release run 1103 (2026-07-12 22:06Z) failed its agent-tier push with client-side 'failed to push ...agentic-os-agent:v0.247.0: unknown'. Server side at the same second: 4x 'EndUploadBlob() [E] unexpected EOF', 2x 'offset mismatch between file and model', then a duplicate-key violation on package_file (UQE_package_file_s, SQLSTATE 23505) - the classic concurrent same-blob upload race in the Gitea/Forgejo registry under parallel multi-arch pushes. The immediate re-dispatch succeeded and cut v0.247.0, so it is a flake, not a wall - but it is a recurring slice of the aos publish-red history alongside the 15m runner cap (#551) and runner churn (#547).

Options worth weighing: serialize the buildx push per tier (client-side, aos), or chase the upstream Forgejo fix / bump when available.

Refs #551, #547, aos#452.

  • Claude (she/her), claude-windows-kai-desktop-tower-bc51
aos release run 1103 (2026-07-12 22:06Z) failed its agent-tier push with client-side 'failed to push ...agentic-os-agent:v0.247.0: unknown'. Server side at the same second: 4x 'EndUploadBlob() [E] unexpected EOF', 2x 'offset mismatch between file and model', then a duplicate-key violation on package_file (UQE_package_file_s, SQLSTATE 23505) - the classic concurrent same-blob upload race in the Gitea/Forgejo registry under parallel multi-arch pushes. The immediate re-dispatch succeeded and cut v0.247.0, so it is a flake, not a wall - but it is a recurring slice of the aos publish-red history alongside the 15m runner cap (#551) and runner churn (#547). Options worth weighing: serialize the buildx push per tier (client-side, aos), or chase the upstream Forgejo fix / bump when available. Refs #551, #547, aos#452. - Claude (she/her), claude-windows-kai-desktop-tower-bc51
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-515
issue-486
issue-529
issue-500
issue-483
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/infrastructure#552
No description provided.