Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

pre-push gate can hang on load-sensitive SLA test while embedding backlog drains

Open
  • Is something wrong?
#689 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
ci-cd, testing

Research direction

Start with tests/test_arbitration.py::test_real_concurrent_writers_keep_interactive_store_searchable_under_sla and trace how the mandatory pre-push hook selects it. Read AGENTS.md alongside the existing exclusions for test_vector_store.py and test_engine.py, then compare the timeout and reclassification options. Done means the pre-push path no longer silently hangs under embedding load and communicates the retry or scope choice clearly.

Written by the indexing model from the issue text.

Description

During the fleet gitignore sweep (2026-08-09), the mandatory pre-push full suite hung >20 min in tests/test_arbitration.py::test_real_concurrent_writers_keep_interactive_store_searchable_under_sla (its own round-trip SLA is 2s). Process sample showed NumPy/GIL work — consistent with the bge embedding model saturating CPU while the W2.5 backlog drain was running, starving the test's concurrent writers.

Standalone repro after load subsided: passes in 3.04s. So the test is correct but load-sensitive, and it sits in the mandatory pre-push path.

Proposed fixes (either):

  1. Bound it: pytest-timeout on this test in the pre-push hook, with a clear "machine under embedding load — retry or use changed-only scope" message instead of a silent hang.
  2. Reclassify it alongside the real-DB deliberate-check set excluded from worker pre-push (AGENTS.md already excludes test_vector_store.py/test_engine.py).

Workaround used: BRAINLAYER_PREPUSH_SCOPE=changed-only (documented scoped path) for the gitignore-only push (#688).

Filed by brainlayerClaude lead (Fable 5).

🤖 Generated with Claude Code

Dominant language
Python
Stars
9
Forks
7
Avg merge
2h 8m
Merged PRs (30d)
211

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EtanHey/brainlayer

All issues in EtanHey/brainlayer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.