Aaron Abbott

Putting this back in draft for now, see the comments on linked issue https://github.com/open-telemetry/opentelemetry-python-contrib/issues/3191#issuecomment-2596409863

@trask it looks like that code triggers the SDK to shut down when the process is ending, which is a separate important issue. This issue is about what the shutdown...

AI for me is to investigate what other SIGs are doing and when this was added to the spec. At SIG, we decided that option 2. would need some spec...

There's some spec discussion here https://github.com/open-telemetry/opentelemetry-specification/issues/1034. One of the things they mentioned is similar to option 2. Let's see if we can get some clarity in the spec.

> BTW do you see what's wrong with the Public API check? I think it's just flaking, the output doesn't have any results even though its failing

Actually @xrmx this PR fixes the check https://github.com/open-telemetry/opentelemetry-python/pull/3825

> BTW changelog would be nice to have the ruff commit handy I didn't add an entry initially because I don't think it's applicable to the changelog audience (consumers of...

Adding "do not merge label" until we decide for sure on Ruff replacing flake8 and pylint as well.

Closing it out as #4223 actually went through

> I'd like the next release of opentelemetry-instrumentation-vertexai to include `google.cloud.aiplatform.v1beta1.PredictionService/StreamGenerateContent` Absolutely I'm working on it now. I also need to support the async API. Should be quite straightforward