-
Notifications
You must be signed in to change notification settings - Fork 89
Close all open files, clean up fsnotify watcher #1268
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
Conversation
|
Codecov ReportAttention: Patch coverage is
@@ Coverage Diff @@
## devel #1268 +/- ##
==========================================
+ Coverage 39.80% 40.12% +0.32%
==========================================
Files 45 48 +3
Lines 9376 10021 +645
==========================================
+ Hits 3732 4021 +289
- Misses 5354 5706 +352
- Partials 290 294 +4
... and 7 files with indirect coverage changes
🚀 New features to boost your workflow:
|
@@ -209,6 +209,14 @@ loop: | |||
MainInstance.nc.GetLogger().Error("Error updating status file %s: %s", statusFilename, err) | |||
} | |||
} | |||
err = stdin.Close() |
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.
Im a bit worried about these two for longer running jobs,
Have you tested this with either
A job lasting longer than 5 min
Using defer
😄
Mostly this looks great! And i think it is probably good as it currently is, but as the code around command is both complicated and critical I want to make sure longer jobs and kube have been tested. |
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.
lgtm
Ty for doing the longer tests
Close all open files, clean up fsnotify watcher to fix fsnotify watcher: too many open files bug