…lization (pythonGH-104826)Disallow thread creation and fork at interpreter finalization.in the following functions, check if interpreter is finalizing and raise `RuntimeError` with appropriate message:* `_thread.start_new_thread` and thus `threading`* `posix.fork`* `posix.fork1`* `posix.forkpty`* `_posixsubprocess.fork_exec` when a `preexec_fn=` is supplied.---------(cherry picked from commitce558e6)Co-authored-by: chgnrdv <52372310+chgnrdv@users.noreply.github.com>Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com>Co-authored-by: Gregory P. Smith <greg@krypto.org>

…alization (GH-104826) (#105277)gh-104690 Disallow thread creation and fork at interpreter finalization (GH-104826)Disallow thread creation and fork at interpreter finalization.in the following functions, check if interpreter is finalizing and raise `RuntimeError` with appropriate message:* `_thread.start_new_thread` and thus `threading`* `posix.fork`* `posix.fork1`* `posix.forkpty`* `_posixsubprocess.fork_exec` when a `preexec_fn=` is supplied.---------(cherry picked from commitce558e6)Co-authored-by: chgnrdv <52372310+chgnrdv@users.noreply.github.com>Co-authored-by: Gregory P. Smith <greg@krypto.org>

In Python 3.12, you cannot pass a preexec_fn to subprocess.Popenduring interpreter shutdown:python/cpython#104826This avoids the problem by giving startProgram an arg to notuse a preexec_fn, and passing that all the way from anaconda'sexitHandler through execWithRedirect and _run_program.Signed-off-by: Adam Williamson <awilliam@redhat.com>

In Python 3.12, you cannot pass a preexec_fn to subprocess.Popenduring interpreter shutdown:python/cpython#104826This avoids the problem by giving startProgram an arg to notuse a preexec_fn, and passing that all the way from anaconda'sexitHandler through execWithRedirect and _run_program.Signed-off-by: Adam Williamson <awilliam@redhat.com>

… python 3.12 (#6859)## Motivation- Make the instrumentation telemetry client compatible with python3.12:python/cpython#104826## Description - Start telemetry worker thread as early as possible. - Delays sending all telemetry events until app-started is queued. - Refactors tests to align with this new logic. ## Risk - Telemetry events (metrics/logs/integrations) are queued as early aspossible but these events are only sent when the trace agent writer isstarted. This **may** result in a memory leak if high cardinalitytelemetry metrics and logs are added in the future. This is not aconcern right now.## Checklist- [x] Change(s) are motivated and described in the PR description.- [x] Testing strategy is described if automated tests are not includedin the PR.- [x] Risk is outlined (performance impact, potential for breakage,maintainability, etc).- [x] Change is maintainable (easy to change, telemetry, documentation).- [x] [Library release noteguidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)are followed. If no release note is required, add label`changelog/no-changelog`.- [x] Documentation is included (in-code, generated user docs, [publiccorp docs](https://github.com/DataDog/documentation/)).- [x] Backport labels are set (if[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))## Reviewer Checklist- [x] Title is accurate.- [x] No unnecessary changes are introduced.- [x] Description motivates each change.- [x] Avoids breaking[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)changes unless absolutely necessary.- [x] Testing strategy adequately addresses listed risk(s).- [x] Change is maintainable (easy to change, telemetry, documentation).- [x] Release note makes sense to a user of the library.- [x] Reviewer has explicitly acknowledged and discussed the performanceimplications of this PR as reported in the benchmarks PR comment.- [x] Backport labels are set in a manner that is consistent with the[release branch maintenancepolicy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)- [x] If this PR touches code that signs or publishes builds orpackages, or handles credentials of any kind, I've requested a reviewfrom `@DataDog/security-design-and-guidance`.- [x] This PR doesn't touch any of that.---------Co-authored-by: Yun Kim <yun.kim@datadoghq.com>Co-authored-by: Tahir H. Butt <tahir.butt@datadoghq.com>Co-authored-by: Gabriele N. Tornetta <gabriele.tornetta@datadoghq.com>Co-authored-by: Yun Kim <35776586+Yun-Kim@users.noreply.github.com>Co-authored-by: Emmett Butler <emmett.butler321@gmail.com>Co-authored-by: ZStriker19 <zach.groves@datadoghq.com>

… python 3.12 (#6859)- Make the instrumentation telemetry client compatible with python3.12:python/cpython#104826 - Start telemetry worker thread as early as possible. - Delays sending all telemetry events until app-started is queued. - Refactors tests to align with this new logic.- Telemetry events (metrics/logs/integrations) are queued as early aspossible but these events are only sent when the trace agent writer isstarted. This **may** result in a memory leak if high cardinalitytelemetry metrics and logs are added in the future. This is not aconcern right now.- [x] Change(s) are motivated and described in the PR description.- [x] Testing strategy is described if automated tests are not includedin the PR.- [x] Risk is outlined (performance impact, potential for breakage,maintainability, etc).- [x] Change is maintainable (easy to change, telemetry, documentation).- [x] [Library release noteguidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)are followed. If no release note is required, add label`changelog/no-changelog`.- [x] Documentation is included (in-code, generated user docs, [publiccorp docs](https://github.com/DataDog/documentation/)).- [x] Backport labels are set (if[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))- [x] Title is accurate.- [x] No unnecessary changes are introduced.- [x] Description motivates each change.- [x] Avoids breaking[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)changes unless absolutely necessary.- [x] Testing strategy adequately addresses listed risk(s).- [x] Change is maintainable (easy to change, telemetry, documentation).- [x] Release note makes sense to a user of the library.- [x] Reviewer has explicitly acknowledged and discussed the performanceimplications of this PR as reported in the benchmarks PR comment.- [x] Backport labels are set in a manner that is consistent with the[release branch maintenancepolicy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)- [x] If this PR touches code that signs or publishes builds orpackages, or handles credentials of any kind, I've requested a reviewfrom `@DataDog/security-design-and-guidance`.- [x] This PR doesn't touch any of that.---------Co-authored-by: Yun Kim <yun.kim@datadoghq.com>Co-authored-by: Tahir H. Butt <tahir.butt@datadoghq.com>Co-authored-by: Gabriele N. Tornetta <gabriele.tornetta@datadoghq.com>Co-authored-by: Yun Kim <35776586+Yun-Kim@users.noreply.github.com>Co-authored-by: Emmett Butler <emmett.butler321@gmail.com>Co-authored-by: ZStriker19 <zach.groves@datadoghq.com>

… python 3.12 (#6859)## Motivation- Make the instrumentation telemetry client compatible with python3.12:python/cpython#104826## Description - Start telemetry worker thread as early as possible. - Delays sending all telemetry events until app-started is queued. - Refactors tests to align with this new logic. ## Risk - Telemetry events (metrics/logs/integrations) are queued as early aspossible but these events are only sent when the trace agent writer isstarted. This **may** result in a memory leak if high cardinalitytelemetry metrics and logs are added in the future. This is not aconcern right now.## Checklist- [x] Change(s) are motivated and described in the PR description.- [x] Testing strategy is described if automated tests are not includedin the PR.- [x] Risk is outlined (performance impact, potential for breakage,maintainability, etc).- [x] Change is maintainable (easy to change, telemetry, documentation).- [x] [Library release noteguidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)are followed. If no release note is required, add label`changelog/no-changelog`.- [x] Documentation is included (in-code, generated user docs, [publiccorp docs](https://github.com/DataDog/documentation/)).- [x] Backport labels are set (if[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))## Reviewer Checklist- [x] Title is accurate.- [x] No unnecessary changes are introduced.- [x] Description motivates each change.- [x] Avoids breaking[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)changes unless absolutely necessary.- [x] Testing strategy adequately addresses listed risk(s).- [x] Change is maintainable (easy to change, telemetry, documentation).- [x] Release note makes sense to a user of the library.- [x] Reviewer has explicitly acknowledged and discussed the performanceimplications of this PR as reported in the benchmarks PR comment.- [x] Backport labels are set in a manner that is consistent with the[release branch maintenancepolicy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)- [x] If this PR touches code that signs or publishes builds orpackages, or handles credentials of any kind, I've requested a reviewfrom `@DataDog/security-design-and-guidance`.- [x] This PR doesn't touch any of that.---------Co-authored-by: Yun Kim <yun.kim@datadoghq.com>Co-authored-by: Tahir H. Butt <tahir.butt@datadoghq.com>Co-authored-by: Gabriele N. Tornetta <gabriele.tornetta@datadoghq.com>Co-authored-by: Yun Kim <35776586+Yun-Kim@users.noreply.github.com>Co-authored-by: Emmett Butler <emmett.butler321@gmail.com>Co-authored-by: ZStriker19 <zach.groves@datadoghq.com>

Python 3.12 introduced a bug during the interpreter shutdown, see:- issuepython/cpython#104826- bugfixpython/cpython#117029With Python 3.12.3, this change could potentially be reverted (after testing).

Python 3.12 introduced a bug during the interpreter shutdown, see:- issuepython/cpython#104826- bugfixpython/cpython#117029With Python 3.12.3, this change could potentially be reverted (after testing).