Strict version constraint on opentelemetry-sdk

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
observability-sre, python
Domain
build-system

Research direction

The strict pin opentelemetry-sdk==1.33.0 lives in the package's dependency declaration, most likely setup.py or a pyproject/requirements file; search the repo for the string. Check whether the server code uses any OpenTelemetry API that changed between 1.33 and 1.43 before loosening the pin. Done means a compatible range is declared and the existing test suite passes, but the maintainers have not replied in 112 days, so confirm the intent in the issue before opening a pull request.

Written by the indexing model from the issue text.

Description

Hi,

I noticed that this package currently pins: opentelemetry-sdk==1.33.0

Is there a specific reason for requiring exactly version 1.33.0, or could this dependency be relaxed to allow newer compatible releases?

The strict pin is causing dependency resolution conflicts in projects that use other packages requiring more recent versions of opentelemetry-sdk (the package is currently at 1.43.0).

From my perspective, a constraint such as: opentelemetry-sdk>=1.33.0,<2.0.0 (or another appropriate compatibility range) would make integration easier while still protecting against breaking changes. Is there any known incompatibility with newer OpenTelemetry SDK versions, or would you be open to relaxing the requirement?

Thanks!

Dominant language
Python
Stars
28
Forks
10
Avg merge
7h 58m
Merged PRs (30d)
10

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 microsoft/azureml-inference-server

All issues in microsoft/azureml-inference-server

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.