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

Python linter uses absent sccache for source dependencies

Open Beginner friendly
#492 1 comment 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
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
cmake, github-actions, python

Research direction

Start by reading the reusable Python linter workflow at v2.5.1 and compare where the CMake compiler launcher variables are set with where sccache is installed, especially for ty jobs with check-stubs false and setup-mlir enabled. Use the linked IBM QDMI Actions run to confirm the /bin/sh: 1: sccache: not found failure. Done when a build job cannot invoke an absent launcher.

Written by the indexing model from the issue text.

Description

🤖 AI text below 🤖

The reusable Python linter at v2.5.1 sets CMAKE_C_COMPILER_LAUNCHER and CMAKE_CXX_COMPILER_LAUNCHER to sccache for every job, but installs sccache only when check-stubs is true. A ty job with check-stubs false and a source-built dependency therefore fails its CMake compiler probe with /bin/sh: 1: sccache: not found.

Observed in the IBM QDMI migration: https://github.com/munich-quantum-software/ibm-qdmi-device/actions/runs/38127562051/job/114435088726 . The dependency is MQT Core at 5f3fc6620f6a731067863ce0a8f2b1afc6f66058; setup-mlir is enabled. Install the launcher whenever a build can occur, or set the launcher variables only when sccache is installed.

Codex diagnosed the failure from CI logs. Acceptance and responsibility remain with the human reviewer.

Dominant language
No language data
Stars
11
Forks
3
Avg merge
4h 49m
Merged PRs (30d)
23

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 munich-quantum-toolkit/workflows

All issues in munich-quantum-toolkit/workflows

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.