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
I am using this library in production for years now and recently gotten in to more and more scenarios
in which apps are crashing because watchers can not be created.
Describe the bug
When a watcher can not be created the application crashes
watcher, err:=fsnotify.NewWatcher()
iferr!=nil {
util.Fatal("failed to create Watcher")
}
Expected behaviour
I either expect this operation to return the error value or at least for the error to be included in the fatal log message
To Reproduce
You would have to create a system state in which fsnotify.NewWatcher() returns an error.
I can't point out the error that caused it in my case, since it is not logged by the library.
This error occurs rarely in some of my containers, the majority work as expected.
System information
tail version: latest
OS: alpine in Docker
Arch: amd64
The text was updated successfully, but these errors were encountered:
I am using this library in production for years now and recently gotten in to more and more scenarios
in which apps are crashing because watchers can not be created.
Describe the bug
When a watcher can not be created the application crashes
tail/watch/inotify_tracker.go
Line 220 in 4472660
Expected behaviour
I either expect this operation to return the error value or at least for the error to be included in the fatal log message
To Reproduce
You would have to create a system state in which
fsnotify.NewWatcher()
returns an error.I can't point out the error that caused it in my case, since it is not logged by the library.
This error occurs rarely in some of my containers, the majority work as expected.
System information
The text was updated successfully, but these errors were encountered: