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
It is fairly common that software will create pipes and then need to re-connect to them later (an example being when using a fifo for streaming logs between processes, and wanting the listener to be able to re-listen in case of a crash or upgrade).
The Pipe API in go-winio unfortunately doesn't support this - as the ListenPipe function will attempt to create the FIFO - and error when it already exists.
Today, I find myself needing to use my fork in a different project, and so now I'd like to try and land this upstream 😅
(I also noticed that someone actually opened a PR with those changes in 2020, but nobody ever got around to reviewing them #170 - I'm happy to open a new PR if this is something that folks would like to add).
The text was updated successfully, but these errors were encountered:
It is fairly common that software will create pipes and then need to re-connect to them later (an example being when using a fifo for streaming logs between processes, and wanting the listener to be able to re-listen in case of a crash or upgrade).
The Pipe API in go-winio unfortunately doesn't support this - as the ListenPipe function will attempt to create the FIFO - and error when it already exists.
I ended up forking go-winio to add a hacky function for this in 2019 (main...endocrimes:go-winio:dani/safe-relisten#diff-c9a2c1c22d0d0cb9afa231de2930c35096c8cda653a3d6fc94e159bfdcd71b7f) that has been in production use in Nomad since then (hashicorp/nomad#5864) - but due to my lack of deep knowledge of Windows API never opened a PR here at the time without knowing how stable it would be.
Today, I find myself needing to use my fork in a different project, and so now I'd like to try and land this upstream 😅
(I also noticed that someone actually opened a PR with those changes in 2020, but nobody ever got around to reviewing them #170 - I'm happy to open a new PR if this is something that folks would like to add).
The text was updated successfully, but these errors were encountered: