Story: Hotfix: nightly CI failures
Table of Contents
This page documents a story in Sprint 30. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
The nightly builds on Linux, macOS and Windows and the valgrind run are red.
The causes are separate: the cli 2.3.0 completion change, one GCC error, one
Windows compile error, a missing valgrind suppression, an uninitialised send,
and three macOS test failures. This story fixes each cause, so that the nightly
runs show only real defects.
2. Status
| Field | Value |
|---|---|
| State | STARTED |
| Parent sprint | Sprint 30 |
| Now | Fixes raised in one PR. |
| Waiting on | Nothing. |
| Next | Confirm the fixes in the nightly run. |
| Last touched | 2026-11-09 |
3. Acceptance
- The 16
ores.shell.*suites pass withcli2.3.0. - The GCC and Windows jobs compile past their reported errors.
- The valgrind run reports no NATS still-reachable defect, and the uninitialised send is fixed or classified.
- The macOS change-stream and next-fire tests pass, and the HTTP client timeout names the test that hangs.
- The nightly runs on
mainconfirm each item.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Scaffold story: Hotfix: nightly CI failures | DONE | 2026-11-09 | 2026-11-09 | Story scaffolding rides this task: documents, sprint wiring, and the scaffold PR. Close it before merging that PR. |
| Implement Hotfix: nightly CI failures | DONE | 2026-11-09 | 2026-11-09 | Initial task for: Hotfix: nightly CI failures |
5. Decisions
- Test the bare verb that
cli2.3.0 returns, and do not patch the overlay.ores.shellruns onCliFileSession, which has no tab completion, so no user sees the completion output. - Carry every fix in one PR with one commit per fix. The nightly runs on
mainare the final proof, because no local environment reproduces macOS or Windows.