-
Notifications
You must be signed in to change notification settings - Fork 22
bug: error on init #127
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
Comments
This is a compatibility issue, which appears in 1.11. Works as expected in 1.10.6 (lts) |
I am having the same issue. I set up a new environment and ran add FundamentalsNumericalComputation as suggested at https://github.com/fncbook/FundamentalsNumericalComputation.jl I received the following warning: ┌ Warning: exception during initialization: 'KeyError(MatrixDepot)' I am running 1.11. Attached is the output for add FundamentalsNumericalComputation |
You can (for the moment) ignore the warning; it is just not possible to write a cache of the internal database. Maybe it is necessary to remove the file |
Okay. Thanks. My plan was to maybe let just let it be. It is not like I need it straight away. |
Okay, will use Julia 1.10.6 in the mean time then. Will there be a fix for this issue for Julia 1.11 in the future? @KlausC |
I am working on it. |
This bug appears differently on nightly builds, I think it is related to this PR: JuliaLang/julia@9dbdeb4 |
I've filed an issue with julia for this: JuliaLang/julia#56916 |
A quick fix for this would be to define a custom serialization to JSON for the |
An even better alternative might be to do this work on first call to |
In general, is MatrixDepot overengineered? The matrix keys correspond to filenames, the core functionality of the package could run entirely on "isfile", "curl", and "mmread", without the need for a centralized database, right? |
When initializing MatrixDepot, there are two errors appearing. I have tried removing and adding the package again without any success.
When running
test MatrixDepot
I get the following output:Is this a bug or am I doing something wrong?
The text was updated successfully, but these errors were encountered: