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
We are noticing sporadic Emit scheduled slot event: epoch already trimmed error logs from scheduler component. This is caused by locking dssMutex:
Emit scheduled slot event: epoch already trimmed
charon/core/tracker/incldelay.go
Line 35 in b098665
Operating System:
What version of Charon are you running? (Which release)
v0.15.0-rc1
Anything else relevant (validator index / public key)?
The text was updated successfully, but these errors were encountered:
core/tracker: unlock mutex (#2027)
0eca4f6
Unlock mutex before doing any i/o in core/tracker/incldelay.go. category: bug ticket: #2028
99c6f29
core/tracker: unlock mutex (#2030)
1dae9e2
Unlock mutex before doing any i/o in core/tracker/incldelay.go. category: bug ticket: #2028 cherry-pick: #2027
67a5e4a
Closed by #2030
Sorry, something went wrong.
dB2510
No branches or pull requests
🐞 Bug Report
Description
We are noticing sporadic
Emit scheduled slot event: epoch already trimmed
error logs from scheduler component. This is caused by locking dssMutex:charon/core/tracker/incldelay.go
Line 35 in b098665
Which blocks emitted slot event error log resulting in error getting logged much later. Look for similar problems wherever we added mutexes.
Has this worked before in a previous version?
Yes, the previous version in which this bug was not present was: v0.14.4🔬 Minimal Reproduction
🔥 Error
🌍 Your Environment
Operating System:
What version of Charon are you running? (Which release)
Anything else relevant (validator index / public key)?
The text was updated successfully, but these errors were encountered: