Sasha Sobol
Sasha Sobol
Hi. Looking at the output, it seems you are right. Somehow the `l.mu` got locked, so we are stuck on `deadlock.go:330 `. I do not see how it could happen....
I found one bug in the library, hopefully fixed it in https://github.com/sasha-s/go-deadlock/commit/1595213edefa28ca5047b00340c63557f9c051d0 Not sure it would solve your problem, but could you pull and try again?
Ideally coati would be split into a client and a server: the client would to indexing (and auto-reindexing), the server would be in browser. This way I could set up...
not as elegant as the browser interface, but would be very nice indeed!
I observed a similar problem (AWS, go). After some debugging, I realized that MacBook decided to sleep during the update (and it messes sleeps, tickers, and timers https://github.com/golang/go/issues/35012 ) The...
@t0yv0 AFAIK go time is _not_ wall time, but monotonic: https://pkg.go.dev/time#hdr-Monotonic_Clocks With the following caveat: > On some systems the monotonic clock will stop if the computer goes to sleep....
Changes look good. Build tags — I know some folks are doing it manually now in their projects when using go-deadlock. If you want to merge your changes in the...
How do you expect panic to work from within OnPotentialDeadlock? It's being called from a separate goroutine when DeadlockTimeout is triggered, so in that case panic would terminate the program....
Could you explain what you are trying to do (A comment in the code would be nice), and illustrate it in a test?
closing because of no activity