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
Double check watch pid if detected as still running on Windows #11513
Conversation
3fb5035
to
3e277fa
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #11513 +/- ##
==========================================
+ Coverage 58.27% 58.40% +0.12%
==========================================
Files 134 135 +1
Lines 11546 11552 +6
==========================================
+ Hits 6729 6747 +18
+ Misses 4153 4143 -10
+ Partials 664 662 -2 ☔ View full report in Codecov by Sentry. |
3e277fa
to
5150b52
Compare
False positives were detected when checking the previous watch process state Signed-off-by: Guillaume Lours <705411+glours@users.noreply.github.com>
5150b52
to
9b0d1ff
Compare
@@ -0,0 +1,29 @@ | |||
//go:build !windows |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As this also applies to Darwin, maybe rename _posix
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙈
What I did
Use an another process management library to double check if the previous watch process is still running or if it's a false positive
Related issue
https://docker.atlassian.net/browse/COMP-25
fix #11066
(not mandatory) A picture of a cute animal, if possible in relation to what you did