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
{{ message }}
This repository has been archived by the owner on Nov 22, 2018. It is now read-only.
I encountered this with multiple writes and a single read. Was unable to reproduce again, despite doing the same thing for the next two weeks. There were over 200 go-routines running at the time of the crash.
If we can't repro, can we put in some recover() at the top of ql somewhere, and collect information (that can be dumped to the console, before rebubbling the panic) that will help debug in the future?
If we can't repro, can we put in some recover() at the top of ql somewhere, and collect information (that can be dumped to the console, before rebubbling the panic) that will help debug in the future?
Provided the error is recoverable, which I don't know, I like the idea. I'm sending you a collaborator's invitation in case you would like to create the patch. If so, please make it a separate branch for easy reviewing before merging it eventually, thank you.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Cf.: fluxcd/flux#393.
The text was updated successfully, but these errors were encountered: