Hi,
Orekit_jpype 13.0.2 is now on pypi.
It also contains one important fix/workaround. Since jpype 1.5.2 dependency there has been an issue with crashes that has been hard to troubleshoot. It seems to be something with the JIT C2 optimizations that makes deallocation of objects fail in the closing (I think). This has now been temporary avoided by turning off the C2 JIT optimizations by providing some jvm startup options. I do not think this has a major performance impact but please report if you find significant reduction in the performance.
If you are willing to investigate, the jpype ticket is at SIGSEGV at end thrown in v1.5.2 but not in previous version · Issue #1261 · jpype-project/jpype · GitHub
Greetings,
3 Likes
Correction - jpype 1.5.2 does not work yet on windows due to Jpype 1.5.1 does not work on Windows (#12) · Issues · Orekit / orekit_jpype · GitLab - reverting to jpype 1.5.0. New packets on pypi.
Hi @petrus.hyvonen thanks a lot for the work.
We recently tried to upgrade our orekit_jpype version from 12 to 13, but we are seeing some issues on our CI with incompatibilities between jpype and pytest. The specific issue we are facing is described here PyTest failure in Python 3.11 and above caused by calling a method that throws in a generated class · Issue #1178 · jpype-project/jpype · GitHub and we are using the base container of python 3.11, which is debian I believe.
We are not facing this issues in local windows environments.
Seeing that the last ‘bugfix’ releases of orekit_jpype 13 have been changing the jpype dependency around due to other issues, I assume this might be tricky to solve/pinpoint. I see that both master and orekit 12.2.1.1 require jpype==1.5.0 in the repo, but the issue is not present when we revert the orekit_jpype version from 13 to 12 in the same feature branch, so it is very confusing.
EDIT: actually investigating further, in the CI for the tests the package used is jpype 1.5.2 (see here build-wheel: [3.11] (#29240) · Jobs · Orekit / orekit_jpype · GitLab). We will adapt our CI to try to do the same as a temporary workaround, but this inconsistency is a bit strange.
Apologies if this is not the correct place to dicuss this. Not sure if I can open an issue on the orekit_jpype gitlab myself, but let me know if that is the correct course of action.