Server errors when working with wheels
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, python
- Domain
- backend, build-system
Research direction
Inspect the Docker build steps that create and copy the wheels, then compare the resulting package set with the requirements.txt installation. Reproduce the /departures request using the wheel-based install and check whether the EFA package is present. Done means the wheel-based image serves /departures without the waitress internal server error.
Written by the indexing model from the issue text.
Description
When using
RUN pip install --no-cache /wheels/*
with the wheels built in the first build step, there is an internal server error caused by waitress, when trying to access /departures.
This indicates that /departures is not served, because maybe the EFA package is not properly included.
When using
RUN pip install --no-cache -r requirements.txt
instead, everything is working fine.
Need to find out which wheels are actually built and copied to the second build step.
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100