chore: ignore mutants.out*/, .rivet/mythos/, .rivet/repos/#278
Merged
Conversation
Three transient working-tree paths that have been showing up as untracked across recent sessions: - `mutants.out/` + `mutants.out.old/` — cargo-mutants per-run output. Large (~MB per run), transient, per-developer. cargo-mutants rotates the previous run to `.old` automatically. - `.rivet/mythos/` — slop-hunt agent pipeline workproducts. The pipeline source lives under `scripts/mythos/`; transient outputs (drafts, ranking JSON, comparison reports) belong outside VCS. - `.rivet/repos/` — destination for `rivet sync` external clones. Per-developer working tree, never committed. Sibling tracked `.rivet/` files (agent-context.md, provenance-pending.json) stay tracked. No behaviour change; these were never committed, but they pollute `git status` and risk an accidental `git add .` capture.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
3 tasks
avrabe
added a commit
that referenced
this pull request
May 15, 2026
…284) Three PRs today (#279, #281, and previously #275/#278) failed CI on the same test: `graph_focused_view_renders_svg`. Cause is structural, not a real-flake: the test's `fetch()` helper hardcodes a 5s read timeout, and the focused /graph endpoint takes ~5s on the dogfood corpus (742 nodes, 1477 edges) — BFS frontier + etch layout pass. The test sits exactly on the edge; CI runner load tips it over. Add a `fetch_with_timeout(port, path, htmx, timeout)` variant. Keep the default 5s `fetch()` for everything else. Bump the graph test's deadline to 15s — well past the genuine wall-clock for this endpoint and short enough that a real performance regression still bubbles up. The wall-clock `Instant::elapsed()` log line stays, so an actual slow regression would still be visible in the test output even though the read timeout no longer blocks it. Verified locally: `cargo test -p rivet-cli --test serve_integration graph_focused_view_renders_svg` passes in 2.79s with the new helper. Refs: REQ-007 (CLI surface)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Three transient working-tree paths that have been showing up as untracked across recent sessions:
No behaviour change; none of these were ever committed, but they pollute `git status` output and create a small risk of accidental capture via `git add .`.
Test plan
🤖 Generated with Claude Code