weaviate / weaviate/weaviate-python-client
Distinguish better between server side and client side errors
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 227
- Forks
- 151
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 11
Description
Currently it is hard for our users to distinguish between server and client side errors.
Internally everything is already in place and we should be good if we improve the error messages
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.
Research direction
Start by tracing the existing error handling in the Python client, since the issue says the internal distinction is already in place. Confirm the server-side and client-side paths and update their error messages so users can distinguish them; verify the resulting messages for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100