1. What is committed
Current main (560ad40d19b2, 2026-07-29) carries 86 local run-output files, 1,342 KiB, at the repository root:
- 13 soak output directories:
soak30-linux/, soak30-mac/, soak-mac2/ through soak-mac6/, soak-mac-fixed/, soak-mac-par/, soak-mac-pool/, soak-mac-st/, soak-ql-mac/, soak-ql-mac-fixed/
- 4 memlab files:
memlab-linux.jsonl, memlab-linux.log, memlab-mac.jsonl, memlab-mac.log
The largest are soak30-linux/cbm-daemon.log (1,778 lines), soak30-linux/latency.csv (1,734 lines), soak30-mac/cbm-daemon.log (1,718 lines), and soak30-mac/latency.csv (1,674 lines). Together these files account for roughly 14,400 of the +24,558 lines main gained between 97ce23f98271 (2026-07-23) and 560ad40d19b2, so more than half of that range's added lines are run logs rather than code. I spot-checked soak30-mac/cbm-daemon.log and memlab-linux.jsonl and found no absolute home paths or usernames, so this looks like hygiene only, not a data leak.
2. How it got in, with the commit range
7808eee5 ("revert(daemon): drop the connection thread pool", 2026-07-26) added all 86 files alongside the revert, verified with git log --diff-filter=A upstream/main -- <path> per path.a5f9a6da ("chore: drop committed soak residue; gitignore soak output dirs", 2026-07-27) caught the problem class one day later, but only removed soak-results-query-leak/ (2,561 lines) and gitignored soak-results/ and soak-results-query-leak/. The 86 files from 7808eee5 match neither pattern, so they survived the cleanup and are still present at head.
Affected range: 7808eee5..560ad40d19b2 (every commit on main since 2026-07-26 ships the files).
3. Suggested fix
git rm -r soak30-linux soak30-mac soak-mac2 soak-mac3 soak-mac4 soak-mac5 soak-mac6 \
soak-mac-fixed soak-mac-par soak-mac-pool soak-mac-st soak-ql-mac soak-ql-mac-fixed
git rm memlab-linux.jsonl memlab-linux.log memlab-mac.jsonl memlab-mac.log
and widening the .gitignore entries added in a5f9a6da from the two literal directory names to patterns that cover the naming actually in use, for example soak-*/, soak[0-9]*/, and memlab-*, or routing all soak/memlab output under the already-ignored soak-results/.
1. What is committed
Current main (
560ad40d19b2, 2026-07-29) carries 86 local run-output files, 1,342 KiB, at the repository root:soak30-linux/,soak30-mac/,soak-mac2/throughsoak-mac6/,soak-mac-fixed/,soak-mac-par/,soak-mac-pool/,soak-mac-st/,soak-ql-mac/,soak-ql-mac-fixed/memlab-linux.jsonl,memlab-linux.log,memlab-mac.jsonl,memlab-mac.logThe largest are
soak30-linux/cbm-daemon.log(1,778 lines),soak30-linux/latency.csv(1,734 lines),soak30-mac/cbm-daemon.log(1,718 lines), andsoak30-mac/latency.csv(1,674 lines). Together these files account for roughly 14,400 of the +24,558 lines main gained between97ce23f98271(2026-07-23) and560ad40d19b2, so more than half of that range's added lines are run logs rather than code. I spot-checkedsoak30-mac/cbm-daemon.logandmemlab-linux.jsonland found no absolute home paths or usernames, so this looks like hygiene only, not a data leak.2. How it got in, with the commit range
7808eee5("revert(daemon): drop the connection thread pool", 2026-07-26) added all 86 files alongside the revert, verified withgit log --diff-filter=A upstream/main -- <path>per path.a5f9a6da("chore: drop committed soak residue; gitignore soak output dirs", 2026-07-27) caught the problem class one day later, but only removedsoak-results-query-leak/(2,561 lines) and gitignoredsoak-results/andsoak-results-query-leak/. The 86 files from7808eee5match neither pattern, so they survived the cleanup and are still present at head.Affected range:
7808eee5..560ad40d19b2(every commit on main since 2026-07-26 ships the files).3. Suggested fix
and widening the
.gitignoreentries added ina5f9a6dafrom the two literal directory names to patterns that cover the naming actually in use, for examplesoak-*/,soak[0-9]*/, andmemlab-*, or routing all soak/memlab output under the already-ignoredsoak-results/.