Package Details: python-opentelemetry-api 1.40.0-1

Git Clone URL: https://aur.archlinux.org/python-opentelemetry.git (read-only, click to copy)
Package Base: python-opentelemetry
Description: OpenTelemetry Python API
Upstream URL: https://github.com/open-telemetry/opentelemetry-python
Licenses: Apache-2.0
Submitter: carsme
Maintainer: A_Bart
Last Packager: A_Bart
Votes: 2
Popularity: 0.59
First Submitted: 2023-06-19 23:08 (UTC)
Last Updated: 2026-03-17 16:23 (UTC)

Latest Comments

1 2 Next › Last »

a821 commented on 2026-04-17 05:26 (UTC)

@A_Bart: These packages are in extra as of today. I think you just need to remove them from the pkgname array, and also the package functions. 

python-opentelemetry-api
python-opentelemetry-exporter-otlp
python-opentelemetry-exporter-otlp-proto-common
python-opentelemetry-exporter-otlp-proto-grpc
python-opentelemetry-exporter-otlp-proto-http
python-opentelemetry-proto
python-opentelemetry-sdk
python-opentelemetry-semantic-conventions
python-opentelemetry-test-utils

rubin55 commented on 2026-04-01 09:12 (UTC) (edited on 2026-04-01 09:25 (UTC) by rubin55)

What is with the partial?! upstreaming of this package to extra? I randomly noticed that I got an update notification, so I checked:

In extra now:

python-opentelemetry-api
python-opentelemetry-sdk
python-opentelemetry-semantic-conventions

Not in extra (yet?):

python-opentelemetry-opencensus-shim
python-opentelemetry-opentracing-shim
python-opentelemetry-exporter-otlp
python-opentelemetry-exporter-otlp-proto-common
python-opentelemetry-exporter-otlp-proto-grpc
python-opentelemetry-exporter-otlp-proto-http
python-opentelemetry-exporter-prometheus
python-opentelemetry-exporter-zipkin
python-opentelemetry-exporter-zipkin-json
python-opentelemetry-exporter-zipkin-proto-http
python-opentelemetry-propagator-b3
python-opentelemetry-propagator-jaeger
python-opentelemetry-proto

I really hope this is a temporary situation.. not looking forward to splitting this up.

Update: I had a look here, it seems some peeps are currently creating a bunch of repositories for separate parts of python-opentelemetry; I didn't see all of them, but since this is literally minutes ago, I assume it's just a matter of time before all of them appear in extras. I just don't understand why they opted for separate packages instead of a single package base.

A_Bart commented on 2026-03-17 16:34 (UTC)

The randomly stuff is fixed. Also, some test that were failing are added again, with a dedicated env to complete. Benchmark tests have been removed, and test that require network run in isolation. The build number has not been bumped, to not cause unnecessary rebuilds.

vikingowl commented on 2026-03-16 16:45 (UTC)

check() fails non-deterministically when python-pytest-randomly is installed

pytest auto-loads the randomly plugin if present, which randomizes test execution order. The test suite relies on global state (propagators, Prometheus registry, providers) that breaks under random ordering — upstream avoids this by isolating each sub-package in its own tox env.

Different seeds = different failures each build (test_propagation, test_label_order_does_not_matter, etc.), making it impossible to fix by deselecting tests.

Fix — one line in check():

-    pytest "$path" "${pytest_args[@]}"
+    pytest "$path" -p no:randomly "${pytest_args[@]}"

User workaround: paru -S <package> --mflags "--nocheck" or uninstall python-pytest-randomly before building.

medaminezghal commented on 2026-03-06 09:48 (UTC) 

_______________________________________ TestDefaultGlobalPropagator.test_propagation _______________________________________

self = <test_global_httptextformat.TestDefaultGlobalPropagator testMethod=test_propagation>

    def test_propagation(self):
        traceparent_value = (
            f"00-{format_trace_id(self.TRACE_ID)}-"
            f"{format_span_id(self.SPAN_ID)}-00"
        )
        tracestate_value = "foo=1,bar=2,baz=3"
        headers = {
            "baggage": ["key1=val1,key2=val2"],
            "traceparent": [traceparent_value],
            "tracestate": [tracestate_value],
        }
>       ctx = extract(headers)
              ^^^^^^^^^^^^^^^^

opentelemetry-api/tests/propagators/test_global_httptextformat.py:42: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

carrier = {'baggage': ['key1=val1,key2=val2'], 'traceparent': ['00-12345678901234567890123456789012-1234567890123456-00'], 'tracestate': ['foo=1,bar=2,baz=3']}
context = None, getter = <opentelemetry.propagators.textmap.DefaultGetter object at 0x7fc19881e270>

    def extract(
        carrier: textmap.CarrierT,
        context: Optional[Context] = None,
        getter: textmap.Getter[textmap.CarrierT] = textmap.default_getter,
    ) -> Context:
        """Uses the configured propagator to extract a Context from the carrier.

        Args:
            getter: an object which contains a get function that can retrieve zero
                or more values from the carrier and a keys function that can get all the keys
                from carrier.
            carrier: and object which contains values that are
                used to construct a Context. This object
                must be paired with an appropriate getter
                which understands how to extract a value from it.
            context: an optional Context to use. Defaults to root
                context if not set.
        """
>       return get_global_textmap().extract(carrier, context, getter=getter)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
E       AttributeError: 'NoneType' object has no attribute 'extract'

tmp_install/usr/lib/python3.14/site-packages/opentelemetry/propagate/__init__.py:101: AttributeError

romainhk commented on 2026-01-12 07:51 (UTC)

I managed to solve my issue with python-opentelemetry. Check stage was using a pytest version from an old pyenv 3.9 folder i have ¯_(ツ)_/¯ I just removed this env and it managed to recover the right one. Hope it can help you @PhCl

But I still have some trouble to install mistral-vibe after solving that (No module named build).

PhCl commented on 2026-01-12 05:22 (UTC)

I also run into the ModuleNotFoundError: No module named 'opencensus' error now. But surprisingly only on one machine, while on a second, relatively comparable installation, it was able to upgrade. To the best of my knowledge, the dependencies come all through "aur/mistral-vibe" in my case, and I did not spot any relevant differences between the setup that worked and the one that failed.

I tried to debug, but unfortunately could not find out more than the error message that romainhk already posted. But I can at least confirm that the problem can occur.

rubin55 commented on 2026-01-10 18:25 (UTC)

I noticed just yet with Python 3.14, a test breaks; add a deselect to the check() stage, i.e.:

--deselect=opentelemetry-sdk/tests/context/test_asyncio.py::TestAsyncio::test_with_asyncio

romainhk commented on 2026-01-07 14:44 (UTC)

Hum, so its on my side. Thx @mistersmee. I'll let a note here if i find something interesting

1 2 Next › Last »