Lukas Hering

@Soulthym > Sure will, not sure I'll need fan control tho since the windows trick seemed to work. I'll keep you updated on the matter Have you found a solution...

Have we considered just using `urllib3.util.Retry` instead of rolling our own retry-backoff loop? Docs: https://requests.readthedocs.io/en/latest/user/advanced/#example-automatic-retries

This might be more appropriate in https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/exporter

> > This might be more appropriate in https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/exporter > > @herin049 the main reason I've put this here is its using the `opentelemetry-exporter-otlp-proto-common`. This will be released with any...

Does this not work for you? ``` class TerminationError(Exception): pass def handler(sig, frame): raise TerminationError() signal.signal(signal.SIGTERM, handler) with tracer.start_as_current_span("normal_run_example") as span: span.set_attribute("example.attribute", "normal_execution") os.kill(os.getpid(), signal.SIGTERM) ```

@Helveg See: https://docs.python.org/3/library/signal.html#execution-of-python-signal-handlers I would stick with this approach and see how it works in practice. It's possible there might be some hidden bugs due to the fact that signal-based...

> While removing explicit `AwsLambdaInstrumentor().instrument()` seems OK to me, I am not fully sure on > > * might there be a side effect? did you try the changes here...

@serkan-ozal I was able to test and manually verify that the changes work with Python `3.9`, `3.11`, `3.12`, `3.13` and `3.14`.

> @herin049 I see your solution captures all the logs by default. Does it also fix the issue, so can you exclude the extension logs and only get function and...

@wpessers Updated all `float64` conversions to explicitly check the `ok` result instead of checking for a non-zero return value. Also updated the format string to use `%.0f` instead of casting...