fix: race condition with host in relay #1273
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vladopajic
requested review from
richard-ramos and
chaitanyaprem
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
peerScoreInspectoris called periodically in separate goroutine started bywaku-org/go-libp2p-pubsub. this goroutine can happen to execute simultaneously with goroutine running testTestUpAndDownthus causing race condition.this issue will probably never appear in normal circumstances as waku node will not be started and stopped repeatedly. however it is nice test case to have as it can identify different issues.
Changes
w.hostinpeerScoreInspectorandSetHost.RUnlock()to happen afterRLock()inTopics()for the sake of consistencyHow to test
it's hard to reproduce this issue as it is data race.
Issue
closes #984