Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

ci: rustup clippy component conflict intermittently fails Ubuntu checks

Closed Beginner friendly
  • Is something wrong?
#92 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
60/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, rust
Domain
ci-cd

Research direction

The failing step is "Install pinned Rust" in .github/workflows/check.yml, which is the file to edit, and the same toolchain install is repeated in every job that uses it. Start by finding each place that installs 1.99.0 with clippy and rustfmt, then try the two-step approach the issue suggests: a minimal toolchain install followed by rustup component add. Done means the Ubuntu job passes several runs in a row, and the Windows and macOS jobs behave as before.

Written by the indexing model from the issue text.

Description

area/infra good first issue type/bug

Problem

Check (ubuntu-24.04) intermittently fails in "Install pinned Rust":

error: failed to install component: 'clippy-preview-x86_64-unknown-linux-gnu', detected conflict: 'bin/cargo-clippy'

Seen on dependabot PR #1 and on #91 (2026-10-16); a re-run passes. The runner image's preinstalled toolchain appears to conflict with installing 1.99.0 with --component clippy,rustfmt in one step.

Expected

Toolchain installation is deterministic on all runners.

Acceptance

  • Fix in .github/workflows/check.yml (e.g. install the 1.99.0 toolchain minimal first, then rustup component add --toolchain 1.99.0 clippy rustfmt, or another approach verified against the rustup conflict), applied to every job that installs the toolchain.
  • Evidence: several consecutive green runs on ubuntu, plus windows/macos unchanged.
Dominant language
Rust
Stars
4
Forks
2
Avg merge
2h 28m
Merged PRs (30d)
76

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cristim/AztecCraft

All issues in cristim/AztecCraft

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.