v2.0.0-rc.5 #266
decahedron1
announced in
Announcements
v2.0.0-rc.5
#266
Replies: 1 comment 11 replies
-
How to use
|
Beta Was this translation helpful? Give feedback.
11 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Possibly breaking
cuda
ortensorrt
) are now linked with/MD
instead of/MT
on Windows; i.e. MSVC CRT is no longer statically linked. This should resolve linking issues in some cases (particularly crates using other FFI libraries), but may cause issues for others. I have personally tested this in 2 internal pyke projects that depend onort
& many FFI libraries and haven't encountered any issues, but your mileage may vary.Definitely breaking
ort
now depends onndarray
0.16.wasm32-unknown-unknown
support has been removed.wasm32-unknown-unknown
working in the first place was basically a miracle. Hacking ONNX Runtime to work outside of Emscripten took a lot of effort, but recent changes to Emscripten and ONNX Runtime have made this exponentially more difficult. Given I am not adequately versed on ONNX Runtime's internals, the nigh-impossibility of debugging weird errors,and the vow I took to write as little C++ as possible ever since I learned Rust, it's no longer feasible for me to work on WASM support forort
.ort
in WASM, I suggest you use and/or support the development of alternative WASM-supporting ONNX inference crates liketract
or WONNX.Features
commit_from_url
will be redownloaded.Trainer
API, just like HF'sTrainerCallbacks
! This allows you to write custom logging/LR scheduling callbacks. See the updatedtrain-clm-simple
example for usage details.Fixes
If you have any questions about this release, we're here to help:
#💬|ort-discussions
Love
ort
? Consider supporting us on Open Collective 💖❤️💚💙💛
This discussion was created from the release v2.0.0-rc.5.
Beta Was this translation helpful? Give feedback.
All reactions