You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On some of my build servers (debian 12, openSuse 15.6), I am getting the following error for last two days. I am not sure what changed!
Compiling magika v0.1.0-rc.2 (https://github.com/google/magika#906afc82)
error[E0432]: unresolved import `ort::GraphOptimizationLevel`
--> /home/dilawar/.cargo/git/checkouts/magika-0dc2ca1a149e7051/906afc8/rust/lib/src/builder.rs:15:5
|
15 | use ort::GraphOptimizationLevel;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^ no `GraphOptimizationLevel` in the root
|
help: consider importing this enum instead
|
15 | use ort::session::builder::GraphOptimizationLevel;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error[E0433]: failed to resolve: could not find `Session` in `ort`
--> /home/dilawar/.cargo/git/checkouts/magika-0dc2ca1a149e7051/906afc8/rust/lib/src/builder.rs:55:32
|
55 | let mut session = ort::Session::builder()?;
| ^^^^^^^ could not find `Session` in `ort`
|
help: consider importing one of these structs
|
Either of the following causes the same error.
# magika = { git = "https://github.com/google/magika", features = [ "_test", "serde" ]}
magika = { version = "0.1.0-rc.2", features = [ "_test", "serde" ]}
The text was updated successfully, but these errors were encountered:
dilawar
changed the title
Build failure on some build servers
Build failure on some linux build servers
Nov 23, 2024
dilawar
added a commit
to dilawar/magika
that referenced
this issue
Nov 23, 2024
Yes, there was a new release of ort and cargo seems to consider all pre-release versions compatible (which I'm not sure follows semver). We should use =2.0.0-rc.8 in rust/lib/Cargo.toml. I'll do that next week.
In the meantime (and until next release), the solution is to cargo update --precise=2.0.0-rc.8 ort from the crate that depends on magika.
On some of my build servers (debian 12, openSuse 15.6), I am getting the following error for last two days. I am not sure what changed!
Either of the following causes the same error.
The text was updated successfully, but these errors were encountered: