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
When running the command with Metal features enabled, the UQFF file is not being generated as expected. This issue occurs specifically when using the Metal backend, while the CPU version works without problems.
Steps to Reproduce
Run the following command:
cargo run --features metal -- --isq Q4K -i plain -m microsoft/Phi-3.5-mini-instruct --write-uqff phi3.5-mini-instruct-q4k.uqff
Additional Information
When executing the above command, the following warning messages are displayed:
warning: unused import: `Tensor`
--> mistralrs-core/src/pipeline/isq.rs:10:27
|
10 | use candle_core::{Device, Tensor};
| ^^^^^^
|
= note: `#[warn(unused_imports)]` on by default
warning: unused imports: `IntoParallelRefIterator` and `IntoParallelRefMutIterator`
--> mistralrs-core/src/pipeline/isq.rs:16:52
|
16 | IndexedParallelIterator, IntoParallelIterator, IntoParallelRefIterator,
| ^^^^^^^^^^^^^^^^^^^^^^^
17 | IntoParallelRefMutIterator, ParallelIterator,
| ^^^^^^^^^^^^^^^^^^^^^^^^^^
warning: unused variable: `write_artifacts`
--> mistralrs-core/src/pipeline/isq.rs:142:9
|
142 | write_artifacts: Option<&PathBuf>,
| ^^^^^^^^^^^^^^^ help: if this is intentional, prefix it with an underscore: `_write_artifacts`
|
= note: `#[warn(unused_variables)]` on by default
warning: variable does not need to be mutable
--> mistralrs-core/src/pipeline/isq.rs:145:18
|
145 | let (mut tensors, mapper) = match organization {
| ----^^^^^^^
| |
| help: remove this `mut`
|
= note: `#[warn(unused_mut)]` on by default
warning: `mistralrs-core` (lib) generated 4 warnings (run `cargo fix --lib -p mistralrs-core` to apply 3 suggestions)
Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.23s
Running `target/debug/mistralrs-server --isq Q4K -i plain -m microsoft/Phi-3.5-mini-instruct --write-uqff phi3.5-mini-instruct-q4k.uqff`
The text was updated successfully, but these errors were encountered:
Describe the bug
When running the command with Metal features enabled, the UQFF file is not being generated as expected. This issue occurs specifically when using the Metal backend, while the CPU version works without problems.
Steps to Reproduce
Additional Information
When executing the above command, the following warning messages are displayed:
The text was updated successfully, but these errors were encountered: