We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
receptor is not bubbling up this error message in some situations.
receptor/pkg/workceptor/kubernetes.go
Line 242 in 4addde8
On a system where fsnotify cannot create a watcher, ReadString returns EOF, and line has this content
line
failed to create fsnotify watcher: too many open files
however, we are leveraging EOF to also mean "we are done reading from the pod, all is good"
I think if err is EOF and line is not empty, then we may need to write bubble up line as an error.
We should make sure line is expected to be empty in successfully cases before doing that, however.
The text was updated successfully, but these errors were encountered:
setting these values (or lower) on your system/VM might help replicate the issue
sysctl fs.inotify.max_user_instances=128 sysctl fs.inotify.max_user_watches=65536
Sorry, something went wrong.
No branches or pull requests
receptor is not bubbling up this error message in some situations.
receptor/pkg/workceptor/kubernetes.go
Line 242 in 4addde8
On a system where fsnotify cannot create a watcher, ReadString returns EOF, and
line
has this contentfailed to create fsnotify watcher: too many open files
however, we are leveraging EOF to also mean "we are done reading from the pod, all is good"
I think if err is EOF and
line
is not empty, then we may need to write bubble upline
as an error.We should make sure line is expected to be empty in successfully cases before doing that, however.
The text was updated successfully, but these errors were encountered: