Alex Boten

All yours @ChrsMark

@aabmass will follow up to determine if this is in the spec or not.

As per the spec: >Export() must not block indefinitely, there must be a reasonable upper limit after which the call must time out with an error result (Failure). https://github.com/open-telemetry/opentelemetry-specification/blob/15ac35c174f097b37e4e7b8a3653700bb2e7e763/specification/trace/sdk.md#exportbatch

@aabmass are you still looking at this issue?

From the specification SIG on 19-Nov, it sounds like there isn't a strong need to have the context parameter at this time. Will close this issue in 2 weeks if...

Thanks @pellared

@khaf will an update on this be part of the next patch release?

Will add for context that the configuration working group moved to split the exporters in this PR https://github.com/open-telemetry/opentelemetry-configuration/pull/146

@braydonk it looks like the [original issue](https://github.com/open-telemetry/opentelemetry-collector/issues/882) suggests it could have been part of the same exporter. Note that the configuration working group ended up choosing to go away from...

This bug was uncovered by the linter https://github.com/open-telemetry/opentelemetry-collector/actions/runs/10480357311/job/29027844869?pr=10935