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

Reappearance of segfault in saving non-double arrays, as in #30 #34

Closed
pp-mo opened this issue Sep 29, 2020 · 7 comments
Closed

Reappearance of segfault in saving non-double arrays, as in #30 #34

pp-mo opened this issue Sep 29, 2020 · 7 comments

Comments

@pp-mo
Copy link

pp-mo commented Sep 29, 2020

On removing the workaround we introduced in iris-grib#208, the original signature problem as reported in #30, seems to have reappeared.

Context:

@shahramn
Copy link
Collaborator

shahramn commented Sep 29, 2020

Dear Patrick,
This is fixed in the next release (with ecCodes v2.19.0) Hopefully out in October

@pp-mo
Copy link
Author

pp-mo commented Sep 30, 2020

Ok thanks @shahramn , I think that means there is no real problem here.

@pp-mo pp-mo closed this as completed Sep 30, 2020
@shahramn
Copy link
Collaborator

We have released the new python bindings for ecCodes (as well as a new library version)

@pp-mo
Copy link
Author

pp-mo commented Oct 19, 2020

@shahramn thanks for the update.
We will check it out !

@shahramn
Copy link
Collaborator

Please let me know if all IRIS tests pass

@pp-mo
Copy link
Author

pp-mo commented Jan 27, 2021

We finally got to cut iris-grib v0.16.0
(it's been waiting for Iris 3.0)

All looking fine now, thanks @shahramn .

@shahramn
Copy link
Collaborator

Glad to hear it. And thank you for your patience

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

No branches or pull requests

2 participants