Forgejo rejects report branch push: unable to create temporary object directory

Breadway commented

2026-10-13 12:10:25 +08:00

Owner

Found while pushing existing feature/breadbug-report during BREAD19 integration repair. Confidence high on reproducible transport/storage failure, unknown root cause. Two git push origin feature/breadbug-report attempts returned remote unpack failed: unable to create temporary object directory and remote rejected unpacker error. Local commit ac8f8ab369 is preserved; remote remains9117355. Earlier store branch push succeeded. Blocks report formatting repair publication and exact-head CI. No Hestia access authorized; do not infer disk exhaustion or change remote permissions without diagnostics.

Found while pushing existing feature/breadbug-report during BREAD19 integration repair. Confidence high on reproducible transport/storage failure, unknown root cause. Two git push origin feature/breadbug-report attempts returned remote unpack failed: unable to create temporary object directory and remote rejected unpacker error. Local commit ac8f8ab369c74d91c8c5a794efac1a95687237f4 is preserved; remote remains9117355. Earlier store branch push succeeded. Blocks report formatting repair publication and exact-head CI. No Hestia access authorized; do not infer disk exhaustion or change remote permissions without diagnostics.

Breadway commented

2026-10-13 12:19:15 +08:00

Author

Owner

Authorized read-only Hestia diagnostics: root and /data have104GiB available and28million free inodes; /data is ext4 rw; bread.git/objects owned git:git mode755. Forgejo logs show writes to /data/gitea/queues/common/000460.log failing no space left on device and archive500s despite current free space. Queue log4.2MiB, data24GiB. This is not evidence of current disk/inode exhaustion; possibly latched storage error, root cause not yet established. No remote modifications/restarts/cleanup made.

Breadway commented

2026-10-13 13:33:06 +08:00

Author

Owner

Retry of the preserved report branch push now succeeded: remote feature/breadbug-report advanced to ac8f8ab369. Store branch pushes also succeeded. No remote changes, cleanup or restarts performed. Root cause not established; earlier Forgejo ENOSPC queue errors despite available filesystem space remain diagnostic evidence. Push path currently recovered, incident not yet proven resolved.

Retry of the preserved report branch push now succeeded: remote feature/breadbug-report advanced to ac8f8ab369c74d91c8c5a794efac1a95687237f4. Store branch pushes also succeeded. No remote changes, cleanup or restarts performed. Root cause not established; earlier Forgejo ENOSPC queue errors despite available filesystem space remain diagnostic evidence. Push path currently recovered, incident not yet proven resolved.

Breadway commented

2026-10-20 15:09:47 +08:00

Author

Owner

Not reproducible now, and the blocked work is already published. No Hestia access was used.

The commit the card says could not be pushed (ac8f8ab369) is an ancestor of origin/feature/breadbug-report (now bba90c3) and of origin/main, so the report formatting repair reached the remote and merged.
Pushes to this repo succeeded repeatedly today, including more than a dozen branch updates for the breadbug stack (upload, status, release, consent, reload, gui) and a throwaway probe branch pushed from a fresh worktree and then deleted. None returned unable to create temporary object directory.

That error pointed at a transient server-side storage condition on the Forgejo host at the time, which has cleared. The original root cause was never established and I did not infer one. If it recurs, capture the push output and the time and check the Forgejo repository's temp/object directory permissions and disk on the host then; reopen this card with that.

Not reproducible now, and the blocked work is already published. No Hestia access was used. - The commit the card says could not be pushed (ac8f8ab369c7) is an ancestor of origin/feature/breadbug-report (now bba90c3) and of origin/main, so the report formatting repair reached the remote and merged. - Pushes to this repo succeeded repeatedly today, including more than a dozen branch updates for the breadbug stack (upload, status, release, consent, reload, gui) and a throwaway probe branch pushed from a fresh worktree and then deleted. None returned `unable to create temporary object directory`. That error pointed at a transient server-side storage condition on the Forgejo host at the time, which has cleared. The original root cause was never established and I did not infer one. If it recurs, capture the push output and the time and check the Forgejo repository's temp/object directory permissions and disk on the host then; reopen this card with that.

Rows
Columns

Forgejo rejects report branch push: unable to create temporary object directory #38