-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Deadlocks in Execute #31
Comments
Thanks for the report. I'm assuming #32 will fix this, but I will leave this issue open. Note that this will not fix the underlying issue (a panic?). |
Thanks for the quick fix! We'll update and monitor |
@bep I've been running into issues updating the package. Is it possible that This is the panic I'm getting:
|
I don't know, but I could/should certainly bump that/the dependenccies. I will do that, thanks for the input. |
See bep/godartsass#31 for some context.
See bep/godartsass#31 for some context.
Thanks, I was able to upgrade to the new release smoothly |
@benlife5 does this mean that this issue is resolved and can be closed? |
I think so. The deadlocks occurs infrequently so I can't say for certain that it is no longer happening but I'm good with closing this item and I can reopen if it recurs. |
Hi,
We've occasionally been seeing deadlocks in the Execute function. Seems to block the timeout functionality from triggering too. Unfortunately, I don't have a way to reproduce, but I've added additional logging for when it happens and will update this issue if I get more details.
Our usage:
Relevant part of the goroutine trace:
Occurred with version 2.0.0, I've just upgraded to 2.3.0 and will update if it happens again
The text was updated successfully, but these errors were encountered: