← Back to issue list

fix(lint-python): make the linter setup more resilient

View original Github issue

Metadata

Project
starflow
Number
#104
Type
pull request
State
merged
Author
lengau
Labels
—
Created
Updated
Closed

Current evaluation

Merged in commit 0f11847, making Python linter setup retry after apt update to recover from unavailable package indexes.

Resolution: closed resolved

Reason: PR #104 was approved and merged with all CI checks passing. It adds an apt update and retry fallback for transient Python linter setup failures.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Try setting up the linters, but if it breaks try again after an apt update. It's written this way because mostly we don't need apt-get update and it just makes the job take longer, but when we do need it it's because a package deb got removed that makes the linter setup fail. This gets fixed automatically when GitHub rebuilds the image. Example breakage: https://github.com/canonical/charmcraft/actions/runs/20105487204/job/57702635457?pr=2524 Example run with the fix: https://github.com/canonical/starflow/actions/runs/20109782715/job/57703659987?pr=104#step:5:38

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Merged in commit 0f11847, making Python linter setup retry after apt update to recover from unavailable package indexes.
stealth/space-bunny-alpha — closed resolved Merged #104 as 0f11847, adding a fallback apt update and linter-setup retry when initial package installation fails.
qwen/qwen3.6-35b-a3b — — Merged a fix to improve Python linter setup resilience. The change adds an apt update fallback to prevent failures when a package deb is removed. Approved by reviewers and passed all CI checks.
qwen3.6-35b-a3b-mtp-q6 — — Merged a fix that makes Python linter setup resilient by retrying after apt update if package installation fails, resolving intermittent CI failures.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/charmcraft#2524 (confidence 85%)

    Its failed CI run demonstrated the package-index failure that motivated the retry.

Related issues

No related issues found above the similarity threshold.