-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Migrate the use of fsnotify to fswatcher in cert_watcher.go #4232
Conversation
Signed-off-by: haanhvu <[email protected]>
@yurishkuro You said here that we need to make both Please help review! |
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.
👍
Codecov ReportBase: 97.10% // Head: 97.10% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #4232 +/- ##
=======================================
Coverage 97.10% 97.10%
=======================================
Files 302 302
Lines 17683 17685 +2
=======================================
+ Hits 17171 17173 +2
Misses 412 412
Partials 100 100
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@@ -34,6 +35,11 @@ func (f *fsnotifyWatcherWrapper) Add(name string) error { | |||
return f.fsnotifyWatcher.Add(name) | |||
} | |||
|
|||
// Close closes the watcher. | |||
func (f *fsnotifyWatcherWrapper) Close() error { |
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.
please add a test for this func
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.
Ok I'll do it.
Is there any command that checks Codecov failure locally? I ran make test
and as I can remember it didn't report the failure.
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.
Not to my knowledge. You can only compare package level coverage before and after the change with go test -cover.
Signed-off-by: haanhvu <[email protected]>
Head branch was pushed to by a user without write access
🎉 Thanks! |
…acing#4232) Signed-off-by: haanhvu <[email protected]> ## Which problem is this PR solving? First step for jaegertracing#3924 as discussed [here](jaegertracing#3924 (comment)) --------- Signed-off-by: haanhvu <[email protected]>
…acing#4232) Signed-off-by: haanhvu <[email protected]> ## Which problem is this PR solving? First step for jaegertracing#3924 as discussed [here](jaegertracing#3924 (comment)) --------- Signed-off-by: haanhvu <[email protected]> Signed-off-by: shubbham1215 <[email protected]>
Signed-off-by: haanhvu [email protected]
Which problem is this PR solving?
First step for #3924 as discussed here