weaviate / weaviate/weaviate-python-client
Handle aborts in notebook environments
Open
Nobody has claimed this yet.
usability
- Dominant language
- Python
- Stars
- 227
- Forks
- 151
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 11
Description
When doing keyboard interruption in Jupyter notebook, users lose the errors on the collection or client objects.
We should add a way that users can access the errors in case of an interrupt
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 keyboard interruption handling for collection and client objects in the Python client when run in a Jupyter notebook. Define how errors should remain accessible after an interrupt, then add coverage for that behavior and verify that errors are retained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter, python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100