tests: attribute missing configured-wrapper version trace in broad feedback
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- bun, typescript
- Domain
- testing
Research direction
Start with packages/ui-server/tests/brain-client.test.ts:553-558 and the retained original/control logs; compare the reported broad run with the passing one-file control without treating the control as a repair. Reproduce the broader sequence or collect bounded probe, spawn, and trace-publication observations to distinguish cache, setup/order, and publication explanations. Done means documenting an evidence-backed cause and correction with focused and selected hosted qualification, or recording the remaining reproduction gap while preserving the stated assertions and guards.
Written by the indexing model from the issue text.
Description
Observation
During #960 verification, bun run check:pr --base 3dc08df98e155d08b9feda38ceb05ce68e82415f at source 3eae038d092c7ea8f498f5b02e0c164bedb385cd, Bun 1.4.3, passes 724 fast cases, then its broad import-feedback run records 4,804 pass / 1 fail across 349 files in 3,374.45 seconds.
The failure is an app spawns through its configured wrapper, not the ambient one (#1363) at packages/ui-server/tests/brain-client.test.ts:553-558: the configured wrapper trace lacks the expected --version argument. The recorded trace does contain configured search, scratch-prune and sync invocations. The first version assertion fails before later ambient-wrapper assertions execute, so this observation alone does not establish wrong-wrapper execution, a privilege-boundary failure or a cause.
An independently recorded one-file control on 76f6b903f6185baab7e1f2677a43b32b6435bbf3 runs bun run test packages/ui-server/tests/brain-client.test.ts: 35 pass / 0 fail / 95 assertions, 17.50 seconds. The test and CLI client source are byte-identical between those sources, but the broader base history and execution context differ. This passing reduction is not a repair or explanation of the failed broad run. The failed broad command was not repeated unchanged. Complete original/control logs are retained.
Supports #736 by reference; relates to the existing #1363 wrapper contract. This is distinct from #1939 controlled version-probe deadline work and #1310's helper-PID observation.
Scope and acceptance criteria
- Preserve the original source/runtime/order and missing-version trace without inferring an ambient-wrapper result.
- Reproduce the broader sequence or obtain bounded probe/spawn/trace-publication observations identifying where the expected invocation is lost or absent. Distinguish cache, setup/order and publication explanations using evidence.
- Keep the configured-versus-ambient wrapper assertions for version, search and sync, real child lifecycle checks and offline guards.
- If a defect is established, scope its correction and meaningful failing/restored proof; otherwise document the remaining reproduction gap. Obtain appropriate focused and selected hosted qualification for any correction.
Out of scope
Voice implementation, speculative production changes, weakened assertions, raised deadlines and an unchanged broad retry until green.
Contract impact
None established. A verification observation, not a selected public behavior change.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 4h 40m
- Merged PRs (30d)
- 953
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from schlessera/brain-kit
-
agent-ready area: backends priority: p2 type: docs
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
schlessera/brain-kit#2383 ·
Maintainers usually reply within 1 day
-
agent-ready area: ci area: docs priority: p2 type: docs
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
schlessera/brain-kit#2104 · 4 comments ·
Maintainers usually reply within 1 day
-
agent-ready area: backends priority: p2 type: test
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
schlessera/brain-kit#1996 · 1 comment ·
Maintainers usually reply within 1 day
-
agent-ready area: docs priority: p2 type: docs
Difficulty 1/5 Under an hour Newbie friendliness 88/100
schlessera/brain-kit#1990 · 3 comments ·
Maintainers usually reply within 1 day
-
agent-ready area: core type: docs
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
schlessera/brain-kit#1944 ·
Maintainers usually reply within 1 day
All issues in schlessera/brain-kit
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
endora-commerce/endora-commerce#397 ·
Maintainers usually reply within 1 day
-
level/task
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
wazuh/wazuh-dashboard-plugins#9472 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
xavxyz/bei-shan-lin-shui#57 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
opennextjs/opennextjs-cloudflare#1461 ·
Maintainers usually reply within 1 day