Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

pre-push hook wedges indefinitely (5h19m observed) — silently converts "pushed" into "didn't"

Aperta
  • Qualcosa non va?
#730 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
git, python, shell
Ambito
developer-experience, devtools, testing

Direzione di ricerca

Start with .githooks/pre-push and scripts/run_tests.sh, then reproduce the hanging push while checking which gate is still running. Trace the reported uv/pytest, lock, file-descriptor, or child-process behavior without assuming the cause. Done means each gate reports progress, hangs fail loudly within its timeout, and the existing test or CI path confirms normal pushes still work.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Observed 2026-08-20 on brainlayer main checkout.

git push with the pre-push hook ran 5h 19m on one attempt and hung past 10 minutes on a second, with no test process alive underneath (pgrep pytest empty while .githooks/pre-push + scripts/run_tests.sh sat at 05:19:48 elapsed). A full suite normally takes ~14 minutes.

Impact is worse than a slow gate: the push never lands, the shell reports nothing, and the agent believes the branch is pushed. PR #727 sat at the OLD head for hours while its fixes were committed locally — the false-"pushed" state was caught only because Etan checked the live PR head. A gate that hangs converts "pushed" into "didn't" with no signal.

Asks:

  1. Hard timeout inside .githooks/pre-push (per-gate, not just overall) that FAILS LOUDLY rather than hanging.
  2. Find the wedge: likely a gate waiting on something that never arrives (uv/pytest child reaped, lock, or a fd/EMFILE condition — the Codex lane on the same tree reported EMFILE on a broad pytest run the same morning).
  3. Progress output so a hung gate is visibly hung.
  4. Until fixed: agents must verify a push by git log origin/<branch> or the PR headSha, never by the absence of an error.

Workaround used: git push --no-verify with CI as the gate, declared explicitly in the PR/collab.

🤖 Generated with Claude Code

Lingua principale
Python
Stelle
9
Fork
7
Merge medio
2h 8m
PR unite (30g)
225

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di EtanHey/brainlayer

Tutte le issue di EtanHey/brainlayer

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.