You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS: Windows 11
Python version: 3.12.10
Package version: 1.33.0
What happened?
See repro & expected
Steps to Reproduce
Programmatically start a Python program via opentelemetry-instrument wrapper.
Observe the process hierarchy.
Expected Result
The started program should stay in the process tree, e.g.
launcher program (grandparent)
|--> opentelemetry-instrument.exe (parent)
|--> started program (child)
The telemetry wrapper should keep running (forwarding stdin/stdout/stderr and CTRL_C to the started program as necessary).
Actual Result
The started program is not part of the launched program process tree. opentelemetry-instrument.exe process exits immediately after the started program is launched.
Additional context
This behavior breaks development tools like .NET Aspire, which rely on the fact that child processes are part of the same process tree to discover all children and clean them up during shutdown.
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered:
Describe your environment
OS: Windows 11
Python version: 3.12.10
Package version: 1.33.0
What happened?
See repro & expected
Steps to Reproduce
opentelemetry-instrument
wrapper.Expected Result
The started program should stay in the process tree, e.g.
The telemetry wrapper should keep running (forwarding stdin/stdout/stderr and CTRL_C to the started program as necessary).
Actual Result
The started program is not part of the launched program process tree.
opentelemetry-instrument.exe
process exits immediately after the started program is launched.Additional context
This behavior breaks development tools like .NET Aspire, which rely on the fact that child processes are part of the same process tree to discover all children and clean them up during shutdown.
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: