StructuralIdentifiability fails to precompile under Julia v1.11 #364
Comments
|
@B-LIE |
|
Thanks for bring this up. I met the same bug. |
|
This should be fixed in 1.11.2 |
|
Hello, Precompiling VSCodeServer... |
|
@TugbaAkmanTR |
|
Julia v1.11.2 just came out. I'm trying to install (@v1.11) pkg> update
Updating registry at `C:\Users\Bernt\.julia\registries\General.toml`
No Changes to `C:\Users\Bernt\.julia\environments\v1.11\Project.toml`
No Changes to `C:\Users\Bernt\.julia\environments\v1.11\Manifest.toml`
Precompiling project...
Progress [==============> ] 1/3
◒ StructuralIdentifiability
✗ Symbolics → SymbolicsLuxExt |
|
OK -- I stopped the precompilation, which has been hanging for some 20 minutes as indicated above. When removing (@v1.11) pkg> update
Updating registry at `C:\Users\Bernt\.julia\registries\General.toml`
Installed Atomix ─ v1.0.0
Updating `C:\Users\Bernt\.julia\environments\v1.11\Project.toml`
[961ee093] ↑ ModelingToolkit v9.51.0 ⇒ v9.54.0
[0c5d862f] ↑ Symbolics v6.15.4 ⇒ v6.22.0
Updating `C:\Users\Bernt\.julia\environments\v1.11\Manifest.toml`
[a9b6321e] ↑ Atomix v0.1.0 ⇒ v1.0.0So Anyways, still something not quite working. I don't get the error messages I got before, but precompilation hangs. |
|
Thank you for reporting! I will look into this at the end of the week. |
|
So precompilation was hanging. For now, I just removed it and made a new release 0.5.10 which works for me on 1.11. |
The upcoming release (0.5.11, I will make it right away) is compatible with the latest versions of ModelingToolkit and Symbolics. |
|
Yaaaay! Thanks Gleb. |
StructuralIdentifiability fails to precompile under Julia v1.11 🐞
I get an error message regarding precompilation.
Expected behavior
Precompilation without error message
Minimal Reproducible Example 👇
See below:
Error & Stacktrace⚠️
See above.
Environment (please complete the following information):
using Pkg; Pkg.status()using Pkg; Pkg.status(; mode = PKGMODE_MANIFEST)versioninfo()Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: