Improve common error messages
Open
@GregoryComer is already working on this.
Since Feb 6, 2025.
module: user experience
triaged
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
🚀 The feature, motivation and pitch
This is a tracking task for improving clarity on common error messages seen by users, based on early adopter experiences and filed issues.
- Tensor size errors
- Input DType mismatch
- Include EValue tag names in string error messages
- Include error enum strings for top-level errors in common locations (pybinding code, method load, method execute)
Feel free to add any additional error messages that we can improve in the comments.
Alternatives
No response
Additional context
No response
RFC (Optional)
No response
cc @mergennachin @byjlw
Contributor guide
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.
Assessment
This issue has not been assessed yet.