Riccardo Magliocchetti

> > Wouldn't be simpler doing the other way around? It's not a module that I expect will grow in scope. What do you think? > > We want [the...

This is not a fix, this is a workaround to avoid the error.

Yeah but the problem is that we expect to go into that loop, the problem to solve is finding out why we don't

Have you seen #4042?

A test has been added, here there are some hints on how to continue the work https://github.com/open-telemetry/opentelemetry-python/pull/4172#issuecomment-2365295127 But first you need to build some confidence with python typing I guess.

We added pyright typechecking to our CI, we can close this

> Note to self: need to run a gunicorn app with this to understand how it will behaves regarding Resources lifetimes Tried: `OTEL_EXPERIMENTAL_RESOURCE_DETECTORS=otel,serviceinstanceid,process opentelemetry-instrument --traces_exporter console --metrics_exporter none --logs_exporter none...

> > Note to self: need to run a gunicorn app with this to understand how it will behaves regarding Resources lifetimes > > I'll give this a try myself....

@Ali-Alnosairi no need to ask on 6 different issues, pick one and eventually open a PR.

Please retry with 2.0.28