mirror of
https://github.com/zml/zml.git
synced 2026-11-16 19:11:09 +00:00
Exe.call panicked when PJRT failed to launch an executable or when a waited execution event reported an error, so a caller could not recover from, say, a device running out of memory. It now returns pjrt.ApiError. A failed launch writes no outputs. With wait, every partition's event is awaited and destroyed, and a failed execution destroys the outputs it wrote, so the results hold no buffer after any error. The neuron and non-neuron event loops become one; their behavior is unchanged. Runner.run and FnExe's Runner.run keep their panic. Direct callers in the examples, the tutorial and zml.testing add try, and the old Loader.loadExecute reports a failed call as LoadFailed; PJRT has already logged its cause. llmd's one direct call follows in its next zml bump. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
History
|
|
|---|---|---|
| .. | ||
| howtos | ||
| learn | ||
| misc | ||
| tutorials | ||
| README.md | ||
Greetings, Programs!
If you want to run our example models, please head over to Getting Started.
Ready to write some code? Try starting with your first model in ZML, or familiarize yourself with the high-level ZML concepts first.
MENU:
Tutorials
- Getting Started : install ZML, run LLama
- Writing your first model
- Simplifying Dimension Handling - Tagged Tensors!
How to ?
- HuggingFace Authentication
- Port Pytorch models to ZML
- Cross Compile and Deploy Models on a Server
- Dockerize Models
- Profile ZML Programs
Learn more...
- ZML Concepts : Tensors, Models, Executables, etc. explained