Skip to content

Make sync.Maps safe for go routines #193

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

Merged
merged 1 commit into from
Jul 30, 2024
Merged

Conversation

ffilippopoulos
Copy link
Member

  • Copy nodeResources data before manipulating to avoid map concurrent modification issues
  • Use pointers to follow structures Go common practice and be lighter in memory when deep copying.

- Copy nodeResources data before manipulating to avoid map
  concurrent modification issues
- Use pointers to follow structures Go common practice and be lighter in
  memory when deep copying.
@ffilippopoulos ffilippopoulos force-pushed the thread-safe-sync-maps branch from 7504987 to a2b5152 Compare July 29, 2024 14:27
@ffilippopoulos ffilippopoulos merged commit 58d6f5a into master Jul 30, 2024
8 checks passed
@ffilippopoulos ffilippopoulos deleted the thread-safe-sync-maps branch July 30, 2024 09:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants