Keep parallel task output readable and bounded
Concurrent test logs interleave half-lines and a noisy task consumes hundreds of megabytes of memory. Prefix complete lines and cap retained output per task.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Streams · Memory limits · Developer experience
Estimated field mix
- Developer tooling60%
- Performance engineering40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A product team waits for every package to rebuild after small changes. An experimental cache is faster but occasionally returns success after a shared type changed. Build a small, auditable task runner around fixture packages.
Setup prerequisites
- Prepare four fixture packages with one shared library and two applications.
- Use only trusted fixture commands in local tests.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Every rendered line carries its task ID without splitting UTF-8 characters.
- Retained output per task stays below a configured byte limit with a visible truncation notice.
- The final summary includes exit code, duration, and an indication that output was truncated.
Implementation constraints
- Handle a final line that has no newline.
- Keep stderr attribution separate from status.
Verification to include
- Emit split multibyte characters from two fixture processes and check rendered text.
- Write beyond the limit and verify bounded retention and a single clear truncation notice.
Deliverables
- Streaming output formatter and noisy-task fixture
Rollout and recovery
Use bounded capture by default and document an explicit file-output option for deeper local debugging.
Value of the work
For the engineer: Practice incremental computation, dependency scheduling, cache correctness, and cancellation.
For the team: Inspect whether faster checks preserve the guarantees reviewers depend on.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.