-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
op-node: Fix race condition closing gossip handler. #8576
Conversation
Warning Rate Limit Exceeded@ajsutton has exceeded the limit for the number of files or commits that can be reviewed per hour. Please wait 13 minutes and 56 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the @coderabbitai review command. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on X ? TipsChat with CodeRabbit Bot (
|
@CodeRabbitSupport It's really annoying that the rabbit posts a comment to say it won't be useful and even more annoying that it tags you to say its not helpful. Similarly it just creates noise when it comments to say it is processing and will comment soon. It would be great if it could be configured to stay completely quiet until it has actual review feedback. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #8576 +/- ##
============================================
- Coverage 34.64% 20.24% -14.40%
============================================
Files 167 88 -79
Lines 7155 2094 -5061
Branches 1209 478 -731
============================================
- Hits 2479 424 -2055
+ Misses 4525 1642 -2883
+ Partials 151 28 -123
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, confirmed it's closed elsewhere.
Description
LogTopicEvents
is callingCancel
on the event handler it logs from. This is done in a go routine butCancel
is not thread safe.Cancel
is called from theblockTopic.Close
function anyway so the log code can simply leave it to that.Metadata