Skip to content

Put a lock around eccodes usage #329

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
Apr 17, 2023
Merged

Conversation

martindurant
Copy link
Member

Might prevent segfaults

#328

Might prevent segfaults
@martindurant
Copy link
Member Author

@emfdavid , this also fixes an ordering thing that might have been the root cause. The lock may then be superfluous, but probably no hindrance.

Copy link
Contributor

@emfdavid emfdavid left a comment

Choose a reason for hiding this comment

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

Hooray! That does it. I was starting to play around with logging exactly where the segfault happens when I saw you email.
Thank you.
Please advise on whether I should pin my build to the merge commit, wait for a 0.1.1 release or make my own patch commit in my fork by cherrypicking your change on
commit b58ad82 (tag: 0.1.0)
Merge: bc3aaff efadcad
Author: Martin Durant [email protected]
Date: Wed Jan 18 20:22:19 2023 -0500

@martindurant
Copy link
Member Author

I'll merge and release right now

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.

2 participants