decentralized-identity / decentralized-identity/universal-resolver
Unable to run current ci/get-driver-status as either python exe of docker container
- Dominant language
- Java
- Stars
- 644
- Forks
- 305
- Avg merge
- 5h 11m
- Merged PRs (30d)
- 1
Description
There seem to be a couple of issues with the get-driver-status utility when following the [readme](https://github.com/decentralized-identity/universal-resolver/tree/main/ci/get-driver-status).
1) Trying to run `pip install --no-cache-dir -r requirements.txt` is failing with
```ERROR: Cannot install -r requirements.txt (line 2) and async-timeout==3.0.1 because these package versions have conflicting dependencies.
The conflict is caused by:
The user requested async-timeout==3.0.1
aiohttp 3.8.5 depends on async-timeout<5.0 and >=4.0.0a3
```
This seems to have been the result of upgrading to aiohttp 3.8.5. Reverting the version back to 3.7.4 from the previous version of requirements.txt resolves the issue but is probably not the right solution.
2) Trying to build the docker version using `docker build -f Dockerfile -t get-driver-status .` is failing due to a Cython issue. A workaround is documented [here](https://discuss.python.org/t/getting-requirements-to-build-wheel-did-not-run-successfully-exit-code-1/30365) and requires constraining Cython<3 when pyaml pulls it in as a dependency.
I am trying to understand why these wouldn't have caused a CI pipeline failure as this utility is used to workout which DID tests to run I thought ?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with ci/get-driver-status/README, requirements.txt, and Dockerfile, then reproduce both the pip dependency conflict and the Docker build failure. Update the dependency constraints so the standalone install and Docker build complete successfully, and verify the utility can run as described in the README.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- ci-cd, devops, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100