[connabyss]

Requested by CH · project thread

What was wrong, what you changed, how you checked:

This PR collects the fixes for 1.0.4. Each one fixes something Bite got wrong on a real project, mostly run on CH's Windows PC. Every fix has its own commit and its own test.

1. Tests that already fail (validator.js). When the first 2 commits fail with nothing taken out, Bite runs the tests once on the newest commit. If they fail there too, it stops, says so, and names the command it ran.
2. A commit's own test skipped on this system (marked e7c4f64c, dotenv 7c675904). Bite now says "skipped: its test … was skipped on Windows" instead of "didn't notice". This also covers a test the commit added inside a parent test that is skipped, where tap names only the parent.
3. UTF-8 output to files. Output to a file is now UTF-8. Output to a pipe keeps the system encoding.
4. Replaced by a later fix (dayjs d0e6738a). Bite now says "➖ replaced by a later fix" instead of "UNDONE".
5. Git submodules (tomlkit, eemeli/yaml). Bite's copies now include each submodule's files.
6. Flaky first run (h2). A first run that fails with nothing taken out now gets one more try, alone.
7. Rewritten later in the same run (h2 #1329). Bite now says "rewritten later by …" when a test notices the rewrite. It also prints a line saying so, so the list matches the summary.
8. --keep-output. This saves each commit's test output, with the change in and with it taken out, to bite_proof/output/<commit>.txt.
9. npm: taking a change out of today's code did nothing (dotenv). git apply inside a copy that sat in the project's git folder changed nothing and still said it worked. It now runs with GIT_CEILING_DIRECTORIES, so git can't see that folder.
10. JavaScript copies moved out of node_modules (validator.js, dayjs). jest, @babel/register and tap skip anything in node_modules, so they skipped Bite's copies too. Copies now sit in the temp folder and link to each of the project's node_modules: a symlink, or a junction on Windows. Removing a copy removes only the link.
11. --only finds older commits. It no longer looks only in the last 40.
12. why: lines. A literal \r and the + diff marker from tap's escaped error dump are now left out.
13. .d.ts files count as code the tests can't run (dayjs).
14. README: adds a "Bite does this / You decide that" box and a link to the Fool Bite challenge (Fool Bite: sneak a "fix" past it (Hack Week challenge) #156).
15. PR template: the pytest box now says it runs tests/selftest.py too, and asks anyone who changes a message to search tests/ for its old wording (what turned fix(recent): say "1 commit", not "1 commits" #163 and fix(recent): refuse --last 0, which can never find a commit #164 red).

Reruns on CH's PC, before and after (commits where a test noticed the change): node-semver 11 → 17, dotenv 8 → 16, dayjs 0 → 9, yaml 0 → 6. All the false alarms we checked by hand are gone.

• Each fix has a test that fails without it.
• python -m pytest passes locally: 315 passed, 1 skipped (that test only runs on Windows). CI is green.

Assisted-by: Claude Code

https://claude.ai/code/session_0175Q8iFhqMpL4wyk62EegnR

---

Generated by Claude Code

[github-actions]

⚠️ Bite: no test noticed 1 change

Bite took the ⚠️ change below out and every test still passed. If it broke later, nothing would warn you. That's fine for a tidy-up, a rename or docs.

Next: if the change should do something, add a test that fails without it.

• ✅ The test test_a_replacement_fix_with_its_own_tests_is_only_noted noticed it was gone. If this change breaks later, that test will warn you.
  _{Commit 871a1d4c: “Note a replacement fix instead of sounding the comeback alarm”}
• ✅ The tests test_node_copies_sit_outside_node_modules_and_see_the_packages and 1 more noticed it was gone. If this change breaks later, they will warn you.
  _{Commit e6660797: “Make JavaScript copies outside node_modules, with a link to it”}
• ✅ The test test_keep_output_saves_what_the_tests_printed noticed it was gone. If this change breaks later, that test will warn you.
  _{Commit 42365ba7: “Add --keep-output: save each commit's test output”}
• ✅ The tests test_marks_survive_output_to_a_file_on_a_cp1252_system and 1 more noticed it was gone. If this change breaks later, they will warn you.
  _{Commit 7dac9bda: “Write UTF-8 to files and pipes; name the test command when tests already fail”}
• ⚠️ No test noticed it was gone. If it breaks later, nothing warns you. Next: add a test that fails without it.
  _{Commit edd94902: “Use one check for --last 0 and --free-checks 0”}
• ✅ The test test_no_still_working_line_after_the_step_ends noticed it was gone. If this change breaks later, that test will warn you.
  _{Commit 2253d3c3: “Wait for a still-working line before a step ends”}
• ✅ The test test_free_checks_zero_is_refused_not_a_silent_all_clear noticed it was gone. If this change breaks later, that test will warn you.
  _{Commit d8be880c: “Refuse --free-checks 0 instead of a silent all-clear”}
• ✅ The test test_a_subtest_added_inside_a_skipped_parent_counts_as_skipped noticed it was gone. If this change breaks later, that test will warn you.
  _{Commit 7979abfa: “Count a subtest inside a skipped parent as skipped”}
• ✅ The test test_a_type_declaration_file_is_code_the_tests_cant_run noticed it was gone. If this change breaks later, that test will warn you.
  _{Commit f048ae53: “Count .d.ts type declarations as code the tests can't run”}
• ✅ The test test_a_why_line_drops_taps_escaped_diff_dump noticed it was gone. If this change breaks later, that test will warn you.
  _{Commit 69280470: “Keep tap's escaped diff dump out of why: lines”}
• ✅ The test test_a_gap_rewritten_later_by_a_noticed_commit_is_skipped noticed it was gone. If this change breaks later, that test will warn you.
  _{Commit 4f1ff54f: “Say so when a flagged commit turns out rewritten later”}
• ✅ The test test_only_finds_a_commit_older_than_the_last_ones_looked_at noticed it was gone. If this change breaks later, that test will warn you.
  _{Commit 070ce1a0: “Let --only find a commit older than the last 40”}
• ✅ The test test_taking_a_change_out_of_a_copy_inside_the_project_changes_the_copy noticed it was gone. If this change breaks later, that test will warn you.
  _{Commit 2c8b0432: “Take a change out of today's code for real on npm projects”}
• ✅ The test test_a_gap_rewritten_later_by_a_noticed_commit_is_skipped noticed it was gone. If this change breaks later, that test will warn you.
  _{Commit a875d295: “Don't flag a change that a later, noticed commit rewrote”}
• ✅ The tests test_tests_that_read_a_submodule_work_on_bites_copies and 2 more noticed it was gone. If this change breaks later, they will warn you.
  _{Commit 77ace169: “Fill git submodules into Bite's copies; rerun a failing baseline once”}
• ✅ The test test_a_pipe_keeps_the_systems_encoding noticed it was gone. If this change breaks later, that test will warn you.
  _{Commit bec9cb6a: “UTF-8 only for output to a file, not a pipe”}
• ✅ The tests test_the_skipped_tests_are_read_by_name and 1 more noticed it was gone. If this change breaks later, they will warn you.
  _{Commit 56cce34c: “Say a commit's own test was skipped here, not that it didn't notice”}
• ✅ The test test_bite_stops_when_the_tests_already_fail_today noticed it was gone. If this change breaks later, that test will warn you.
  _{Commit 053bd8d3: “Stop once when the tests already fail before Bite changes anything”}

_{Bite score for these commits: 17/18 noticed by a test.}

How Bite checks

Bite asks one question about each change: if it disappeared, would any test notice? It takes the change out, runs your tests, and puts it back. The steps to rerun each check yourself are on the job's summary page. What is Bite?