Mark Kittisopikul

Actually, I'm pretty sure the current issue is due to the previous compat bound for libblastrampoline_jll. https://github.com/JuliaRegistries/General/pull/68512/files does not attempt to change Compat.toml. So the existing Compat.toml still applies: https://github.com/JuliaRegistries/General/blob/master/S/SLICOT_jll/Compat.toml

https://github.com/JuliaRegistries/General/pull/68512 has been merged. Now we need to turn our attention to [PeriodicSystems](https://github.com/andreasvarga/PeriodicSystems.jl) we have compat issues over there now.

https://juliahub.com/ui/Packages/Pfapack_jll/HOmkl/0.1.0+1?page=1 Pfapack_jll is registered by the way.

I was looking into mbedtls and its ABI issues. This is mind-boggling: https://github.com/ARMmbed/mbedtls/releases/tag/v2.28.0 > Some fields of mbedtls_ssl_session and mbedtls_ssl_config are in a > different order. This only affects applications...

For what it's worth there is this: https://github.com/JuliaLang/julia/security/policy [email protected]

https://github.com/JuliaImages/ImageMorphology.jl/releases/tag/v0.3.1 now has the `isboundary` function. Can this issue be closed?

You might to check that you are not only running on the main thread, but also the main Task. ``` julia> Base.current_task() === Base.roottask true ```

The other canonical package besides Spark.jl is https://github.com/aviks/Taro.jl I usually test against both Taro.jl and Spark.jl when I make changes to JavaCall

A MWE is really need unfortunately. It's basically impossible for me to look into this without some code that I can execute. I have gleaned that you are doing something...

This is basically a more general JNI issue. If you search `JNI IllegalMonitorStateException` you will find a lot more. In the other issue #131 , I outlined how to tap...