Doctor: name the GPU check images by digest
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
Research direction
Start with the GPU image references in atlas/commands/doctor.py and scripts/atlas-bootstrap.sh, then check how tests are organized. Add a test covering every image reference in both files and ensure each uses a digest; update the relevant line in docs/TROUBLESHOOTING.md with instructions for refreshing a digest. Done when those checks and documentation requirements are covered.
Written by the indexing model from the issue text.
Description
What needs doing
The images of the GPU checks in atlas/commands/doctor.py get a
digest next to the tag, and none uses latest. The Vulkan check
says in its output that it installs packages at run time, or it uses
an image that has them.
The two check images in scripts/atlas-bootstrap.sh (the CUDA
check and the ROCm check, the second by latest) get the same
digests.
Why
A check should run the same image for every user on every day.
docs/TROUBLESHOOTING.md says today that the ROCm check always uses
latest.
Done when
- A test asserts that every image reference in
doctor.pyhas a
digest. - The docs line is updated and says how to refresh a digest.
- The same test reads
scripts/atlas-bootstrap.sh.
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 197
- Avg merge
- 13h 16m
- Merged PRs (30d)
- 124
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a 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 inferstep/ATLAS
-
Bootstrap: the last two steps run as the user who owns the installPossibly taken @assassinationss claimed this 5 days ago. Openarea/install reliability
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
inferstep/ATLAS#412 · 4 comments ·
Maintainers usually reply within 1 day
-
Installer and setup guide: say what the docker group givesPossibly taken @se1vapriya claimed this 6 days ago. Openarea/install documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
inferstep/ATLAS#411 · 5 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
area/cli
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
A `sandbox_subdir` the proxy does not accept is refused, not ignoredPossibly taken @mvanhorn claimed this today. Openarea/proxy reliability
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
inferstep/ATLAS#364 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
area/cli area/lens status/ready
Difficulty 2/5 Half a day Newbie friendliness 66/100
Maintainers usually reply within 1 day
Similar issues
-
[Bug]: Streamed /v1/chat/completions sends unredacted agent error text (keys) in the final chunkPossibly taken @rodricksz4h5 claimed this today. Openarea/streaming comp/gateway P2 type/security
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#138245 ·
Maintainers usually reply within 1 day
-
[oblt-aw][autodoc] Update user onboarding guide for mandatory trigger CODEOWNERS stepPossibly taken @github-actions claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
correction metadata
Difficulty 2/5 Under an hour Newbie friendliness 68/100
acl-org/acl-anthology#10378 · 1 comment ·
Maintainers usually reply within 1 day
-
cloudtrail_multi_region_enabled_logging_management_events fails when the advanced event selector has a custom namePossibly taken @12YYCCYY16 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
prowler-cloud/prowler#13033 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
graygarbage/HermesKey#23 ·