-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[cmd/opampsupervisor]: Fix supervisor on Windows #34570
Labels
Comments
BinaryFissionGames
added
bug
Something isn't working
needs triage
New item requiring triage
labels
Aug 9, 2024
I am currently working on a fix for this and will have a PR out shortly. |
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
/label -needs-triage |
f7o
pushed a commit
to f7o/opentelemetry-collector-contrib
that referenced
this issue
Sep 12, 2024
**Description:** <Describe what has changed.> * Fixed windows improper signalling for the agent to shutdown. * Fixed not closing files in e2e tests (windows will error if a file is not closed when it attempts to delete the temp directory said file is in) * Fixed test config templates quoting (windows filepaths would have trouble since the backslash acts like a character escape) * Added a workflow to allow running e2e tests for windows **Link to tracking Issue:** Closes open-telemetry#34570 **Testing:** * Existing e2e tests cover this. * I've manually tested remotely configuring a windows supervisor with BindPlane. --------- Co-authored-by: Daniel Jaglowski <jaglows3@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
cmd/opampsupervisor
What happened?
Description
Currently, the supervisor doesn't work on windows, nor do our e2e tests work.
The main culprit is the way signals are handled; go does not support sending
os.Interrupt
on Windows. So instead, we'll have to try and send a graceful shutdown signal on windows a different way.Collector version
9a04c69
Environment information
Environment
Windows
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: