Meet an exception when running rust examples with buid.sh
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- debian, rust
- Domain
- machine-learning
Research direction
Start by rerunning ./build.sh rust with RUST_BACKTRACE=1 in the Debian Bookworm environment. Inspect crates/wasi-nn/src/witx.rs at line 45 and the openvino-sys generated functions where ie_core_create fails to load. Done means the Rust examples run without either panic and OpenVINO initializes successfully.
Written by the indexing model from the issue text.
Description
I am using a debian bookworm image. Installed openvino_2024.1.0.15008(using archive). Installed wasmtime-v21.0.1 release. Cloned latest wasi-nn repo.
Meet below exception
$ pwd
/workspace/wasi-nn
$ ./build.sh rust
...
Read graph XML, first 50 characters: <?xml version="1.0" ?>
<net name="mobilenet_v2_1.0
Read graph weights, size in bytes: 13956476
thread 'main' panicked at crates/wasi-nn/src/witx.rs:45:49:
not implemented
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Aborted (core dumped)
I noticed that CI uses a compiled-from-source building, So switched to a new wasmtime build-from-source
$ git clone https://github.com/bytecodealliance/wasmtime --recursive wasmtime
$ cd wasmtime
$ git checkout --track origin/release-21.0.0
$ OPENVINO_INSTALL_DIR=/opt/intel/openvino cargo build -p wasmtime-cli --features wasi-nn
but this time the exception is still there:
Read graph XML, first 50 characters: <?xml version="1.0" ?>
<net name="mobilenet_v2_1.0
Read graph weights, size in bytes: 13956476
thread 'main' panicked at /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/openvino-sys-0.6.0/src/generated/functions.rs:3:1:
`openvino_c` function not loaded: `ie_core_create
Please guide me through. Thanks
- Dominant language
- CSS
- Stars
- 55
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bytecodealliance/wasi-nn
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
bytecodealliance/wasi-nn#109 · 1 comment · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
bytecodealliance/wasi-nn#105 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
bytecodealliance/wasi-nn#98 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
bytecodealliance/wasi-nn#86 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
bytecodealliance/wasi-nn#68 · 4 comments ·
All issues in bytecodealliance/wasi-nn
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
good first issue neural P2
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
selimfirat/pysad#415 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microprediction/timemachines#174 ·