docs(devlog): record WP18 of the 2026-08-08 bug campaign - #1316
Conversation
Published devlog 028/029 as #1314, rebased #1301 onto current dev, and reported #1244's new conflict to its author. The part worth keeping is a retraction, and its own correction. I claimed two CI runs shared a stall signature -- cli-native-profile handing off to cli-restart-health with 'killed 1 dangling process' last -- and posted it to #1302 as a narrowing. False: run 31152916419 never hung at all. It hit the Bun epoll_ctl error while loading autostart-health, kept running, and finished as a failure in 85 seconds. I had compared two logs by memory of what one of them said. Then the retraction itself was wrong twice. It named claude-messages-endpoint as the first affected file in 31263738953, when that is where output stops and baseten-provider is where the error first appears -- two different questions I had collapsed into one column. And it said the EEXIST has 'two outcomes', which asserts causation the logs do not establish: the error appears in all three runs, one of which completed normally. Three passes to state three sentences accurately. Both corrections are public on #1302 with the chain left visible. Also corrected here: 'two cancelled runs at the exact head' was wrong -- they were consecutive heads, before and after the rebase.
github-actions
Bot
added
the
documentation
📝 WalkthroughWalkthroughThe PR adds a WP18 devlog entry covering publication updates, the continued hold of ChangesWP18 leftovers
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@devlog/_plan/260808_bug_campaign/030_wp18_leftovers.md`:
- Line 4: Update the paragraph in 030_wp18_leftovers.md so it does not begin
with the issue identifier `#1301`; prefix it with “issue” while preserving the
existing meaning and references to `#1301` and `#1244`.
- Around line 82-88: Add the text language identifier to the fenced code block
containing the merge-conflict markers in the documented snippet, changing the
opening fence to use text while preserving the conflict-marker content.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 9773b414-ed4e-49b3-9203-09ec964f017d
📒 Files selected for processing (1)
devlog/_plan/260808_bug_campaign/030_wp18_leftovers.md
| # WP18 — the leftovers, and a retraction on #1302 | ||
|
|
||
| Three concrete items remained after WP17: two devlog units unpublished, my own | ||
| #1301 held indefinitely, and #1244 having gone `DIRTY`. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Avoid starting the paragraph with #1301.
Markdownlint reports MD018 for Line 4. Prefix the identifier with issue so the paragraph remains valid Markdown.
Proposed fix
-#1301 held indefinitely, and `#1244` having gone `DIRTY`.
+issue `#1301` held indefinitely, and `#1244` having gone `DIRTY`.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| #1301 held indefinitely, and #1244 having gone `DIRTY`. | |
| issue `#1301` held indefinitely, and `#1244` having gone `DIRTY`. |
🧰 Tools
🪛 markdownlint-cli2 (0.23.2)
[warning] 4-4: No space after hash on atx style heading
(MD018, no-missing-space-atx)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@devlog/_plan/260808_bug_campaign/030_wp18_leftovers.md` at line 4, Update the
paragraph in 030_wp18_leftovers.md so it does not begin with the issue
identifier `#1301`; prefix it with “issue” while preserving the existing meaning
and references to `#1301` and `#1244`.
Source: Linters/SAST tools
| ``` | ||
| <<<<<<< dev (from #1305 / #1163) | ||
| const members = combo.targets.map(target => resolveComboCatalogMember(...)) | ||
| ======= #1244 | ||
| const discoveredMembers = combo.targets.map(target => memberByKey.get(targetKey(target))) | ||
| >>>>>>> | ||
| ``` |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Add a language identifier to the fenced code block.
Markdownlint reports MD040 at Line 82. Use text because this block documents conflict markers rather than executable code.
Proposed fix
-```
+```text📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ``` | |
| <<<<<<< dev (from #1305 / #1163) | |
| const members = combo.targets.map(target => resolveComboCatalogMember(...)) | |
| ======= #1244 | |
| const discoveredMembers = combo.targets.map(target => memberByKey.get(targetKey(target))) | |
| >>>>>>> | |
| ``` |
🧰 Tools
🪛 markdownlint-cli2 (0.23.2)
[warning] 82-82: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@devlog/_plan/260808_bug_campaign/030_wp18_leftovers.md` around lines 82 - 88,
Add the text language identifier to the fenced code block containing the
merge-conflict markers in the documented snippet, changing the opening fence to
use text while preserving the conflict-marker content.
Source: Linters/SAST tools
1 participant
Summary
The last planning document from today's campaign, continuing #1307 and #1314. Docs-only, one file under
devlog/_plan/260808_bug_campaign/.WP18 was cleanup: publish the WP6/WP17 records, rebase my own #1301 which had been held since both its CI runs came back
cancelled, and report #1244's new conflict to its author.The substantive content is a retraction, and that retraction's own correction.
I claimed two CI runs shared a stall signature —
cli-native-profilehanding off tocli-restart-healthwithkilled 1 dangling processas the last line — and posted it to #1302 as a narrowing of the shard-hang investigation. It is false. Run31152916419never hung: it hit the Bunepoll_ctlerror while loadingautostart-health, kept running, and finished as a failure in 85 seconds. I had compared two logs by memory of what one of them said, and cited a completed failure as corroboration for a hang.The retraction was then wrong twice more:
claude-messages-endpointas the first affected file in31263738953, when that is where output stops andbaseten-provideris where the error first appears — two different questions collapsed into one column;EEXISThas "two outcomes", asserting causation the logs do not establish. The error appears in all three runs, one of which completed normally.Three passes to state three sentences accurately. Both corrections are public on #1302 with the chain left visible rather than edited down, since the corrections are the useful part.
Also corrected in the document: "two cancelled runs at the exact head" was wrong — they were consecutive heads, before and after the rebase (
f09ef1557, then454b1d3b5).Verification
bun run privacy:scan— passed (it does readdevlog/)bun test tests/repo-hygiene.test.ts— 11 pass / 0 faildevlog/is outsideci.yml'spaths:Checklist
Summary by CodeRabbit