Introduce SDK as dependency for server
Maintainers usually reply within 4 days
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- docker, python
- Domain
- build-system
Research direction
Review open pull request #611 first, then inspect the Server dependency declaration and the Docker image setup mentioned in the issue. Confirm how the SDK is currently installed and how commit-based compatibility is represented. Done means the Server explicitly installs the SDK from the matching commit and the Docker image uses a compatible SDK version.
Written by the indexing model from the issue text.
Description
Currently, the Server does not have the SDK listed explicitly as dependency, since we didn't know how to make it work, even though it very much depends on the SDK.
The problem is that we need to ensure that a compatible SDK version is installed.
We guarantuee compatibility at a commit basis, so we cannot install the last released sdk, when running the Docker image, for example.
This would mean that we need a way to make sure the Server always installs the SDK of the same commit.
Maybe something like this could work?
dependencies = [
"basyx-python-sdk @ file:../sdk",
]
- Dominant language
- Python
- Stars
- 103
- Forks
- 56
- Avg merge
- 12d 13h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No 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 eclipse-basyx/basyx-python-sdk
-
README CI badge is brokenPossibly taken A pull request linked to this issue is open or already merged. Openbug documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
eclipse-basyx/basyx-python-sdk#656 ·
Maintainers usually reply within 4 days
-
bug server Specification
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
eclipse-basyx/basyx-python-sdk#655 ·
Maintainers usually reply within 4 days
-
bug sdk
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
eclipse-basyx/basyx-python-sdk#634 · 3 comments ·
Maintainers usually reply within 4 days
-
enhancement server
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
eclipse-basyx/basyx-python-sdk#632 ·
Maintainers usually reply within 4 days
-
bug high priority
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
eclipse-basyx/basyx-python-sdk#631 ·
Maintainers usually reply within 4 days
All issues in eclipse-basyx/basyx-python-sdk
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
awslabs/visual-asset-management-system#414 ·
Maintainers usually reply within 1 day
-
bug v1 v2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/python-sdk#3670 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aicell-lab/bioengine#232 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
modelscope/evalscope#1836 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100