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
The goroutine that takes care of deleting the private key lock file when the context is cancelled might not be executed because the Go scheduler didn't schedule it for execution before the main one is.
🔬 Minimal Reproduction
This issue doesn't reproduce 100% of the times, because it's a concurrency issue.
Run a dkg, see if .charon/charon-enr-private-key.lock has been deleted.
The text was updated successfully, but these errors were encountered:
Block `dkg` exit until `privkeylock.Run()` enclosing goroutine exits, ensuring that the private key lock file is always deleted.
`Run()` is supposed to be executed in a goroutine, and since we can't control the scheduler it might be scheduled *after* the `main` one exits, leading to the `ctx.Done()` code path to sometimes never be executed.
category: bug
ticket: #2258
🐞 Bug Report
Description
The goroutine that takes care of deleting the private key lock file when the context is cancelled might not be executed because the Go scheduler didn't schedule it for execution before the main one is.
🔬 Minimal Reproduction
This issue doesn't reproduce 100% of the times, because it's a concurrency issue.
Run a dkg, see if
.charon/charon-enr-private-key.lock
has been deleted.The text was updated successfully, but these errors were encountered: