Handle aborts in notebook environments

Open
#1,300 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@v0ropaev is already working on this.

Since Sep 24, 2026.

  • #2172 by @v0ropaev — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
jupyter, python
Domain
api

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.

Description

usability

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

Dominant language
Python
Stars
230
Forks
173
Avg merge
4d 16h
Merged PRs (30d)
23

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from weaviate/weaviate-python-client

All issues in weaviate/weaviate-python-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.