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

Lens and V3 images: install Python packages from hashed lock files

Open
#333 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@divakantpandey is already working on this.

Since Oct 26, 2026.

  • #661 by @divakantpandey — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
74/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
docker, python

Research direction

Read .github/requirements/ for the hashed lock-file layout, then inspect geometric-lens/Dockerfile and v3-service/Dockerfile. Generate a hashed lock file for each service with pip-compile --generate-hashes, and use --only-binary :all: where every package has a wheel. Done means both images build and pytest geometric-lens/tests and pytest tests/v3-service pass.

Written by the indexing model from the issue text.

Description

area/lens area/v3 docker security status/ready

What needs doing

geometric-lens/Dockerfile and v3-service/Dockerfile install their
Python requirements without hashes, and allow source builds. Generate
a hashed lock file for each service
(pip-compile --generate-hashes), install with --require-hashes,
and add --only-binary :all: where every package has a wheel.

Why

A hashed install fails when a package differs from the one that was
locked. CI already installs its own tools this way.

Done when

  • Both Dockerfiles install with --require-hashes.
  • Both images build, and pytest geometric-lens/tests and
    pytest tests/v3-service pass.

Where to start

  • .github/requirements/ shows the hashed layout CI uses.
  • No GPU is needed.

Refs #202

Dominant language
Python
Stars
2.1k
Forks
197
Avg merge
14h 1m
Merged PRs (30d)
201

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 inferstep/ATLAS

All issues in inferstep/ATLAS

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.