Rust adapter: selective runs on real repositories
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd
Research direction
Start with the Cargo adapter registration and the rust-lang/glob replay pinned in #95, and read #91's out-of-workspace manifest agreement plus #92–#95 for the adapter contract. Compare how existing adapters classify non-code paths and runtime-input tokens, then use those paths as the reference. Done means at least one historical revision in the pinned replay narrows instead of staying FULL, while the selected tests still catch the same failures as the full baseline.
Written by the indexing model from the issue text.
Description
Follow-up to #62. Once #92–#95 merge, the Rust (Cargo) adapter is registered and safe, but it cannot narrow a real repository yet: the pinned rust-lang/glob replay stayed FULL on every revision. This issue tracks the work needed for real-repository selectivity.
Scope
- External dependency inputs. The blockers for non-workspace packages, dependency features or
default-features = false, build scripts and proc macros currently run over every resolved package. Apply them only to the crates a change reaches, wherever the dependency graph can show that. - Runtime-input tokens.
fs,unsafe,exists,metadata,processand similar words in a source file force a repo-wide full run. Narrow this to the owning crate and its dependents. - Out-of-workspace
Cargo.toml. As agreed in #91: treat unmodeled manifests as ownership boundaries and require full validation only when the changed set or its dependents reach them. Keep the repo-wide fallback when metadata can't tell. - CI invocation evidence. Accept common toolchain setup and cache steps (for example
dtolnay/rust-toolchain,Swatinem/rust-cache) when they don't change howcargo testruns. - Non-code paths. Classify
README.md,docs/**and similar files the way the other adapters do, instead of forcing a full run. - Workspace scope. Handle
default-membersand a root[package], where plaincargo testcovers only some members.
Done when a pinned public Rust replay narrows at least one historical revision, and the selected tests catch the same failures as the full baseline.
Maintainer: @FredApps.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 4
- Avg merge
- 18h 41m
- Merged PRs (30d)
- 48
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DiffCI/core
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Planner: splitParts regex is quadratic on a quote followed by many backticks, so the fuzz test fails at randomPossibly taken @FredApps claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Agent tools: changed_files lists only the new path of a renamed filePossibly taken @FredApps claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
adapter good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
agent-ready area: ui-server priority: p3 type: test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
schlessera/brain-kit#4249 ·
Maintainers usually reply within 1 day
-
documentation tool triaged
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
can1357/oh-my-pi#19608 · 2 comments ·
Maintainers usually reply within 1 day
-
dependencies tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bcgov/nr-waste-plus#1549 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-tx-parse#18 ·