Describe the bug
When errors occur, it is important to get the error message logged out. Otherwise it can get very annoying to debug. I have for example hit the following error:
|
util.Fatal("failed to create Watcher") |
I don't know why fsnotify.NewWatcher() would fail, but since the error message isn't included in the error log, it is almost impossible to debug.
Expected behaviour
I would expect the error message is a part of the logs using something like the following:
util.Fatal(fmt.Sprintf("failed to create Watcher: %v", err))
Additional context
I actually came onto this error by using https://github.com/hpcloud/tail which is used in https://github.com/kubeflow/katib.
Describe the bug
When errors occur, it is important to get the error message logged out. Otherwise it can get very annoying to debug. I have for example hit the following error:
tail/watch/inotify_tracker.go
Line 220 in ba755e4
I don't know why
fsnotify.NewWatcher()would fail, but since the error message isn't included in the error log, it is almost impossible to debug.Expected behaviour
I would expect the error message is a part of the logs using something like the following:
Additional context
I actually came onto this error by using https://github.com/hpcloud/tail which is used in https://github.com/kubeflow/katib.