Skip to content
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

Don't lock across update() #466

Closed
wants to merge 1 commit into from
Closed

Don't lock across update() #466

wants to merge 1 commit into from

Conversation

henryr
Copy link

@henryr henryr commented Jul 24, 2024

update() might lock mu when it calls getTargets(). Which would deadlock. Instead, let's make it much narrower in scope and just copy resolvers.

Signed-off-by: Henry Robinson <hrobinson@slack-corp.com>
Copy link
Collaborator

@demmer demmer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree this is a safer approach than what is currently merged, but as mentioned in thread, this is somewhat moot with #465 since in that approach we spin up separate goroutines to call update() and therefore don't deadlock.

Copy link

This PR is being marked as stale because it has been open for 30 days with no activity. To rectify, you may do any of the following:

  • Push additional commits to the associated branch.
  • Remove the stale label.
  • Add a comment indicating why it is not stale.

If no action is taken within 7 days, this PR will be closed.

@github-actions github-actions bot added the Stale label Aug 24, 2024
Copy link

This PR was closed because it has been stale for 7 days with no activity.

@github-actions github-actions bot closed this Aug 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants