weaviate / weaviate/weaviate-python-client
Return correct UUID for failed objects
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 227
- Forks
- 151
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 11
Description
for failed_object in failed_objects:
failed_uuids.add(failed_object.original_uuid)
LOGGER.error(f'Unexpected exception {failed_object.message} creating weaviate object {failed_object.original_uuid}')
This original_uuid seems to be none in some cases
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 failed_objects handling shown in the issue and find where original_uuid is assigned or lost. Confirm the cases where it is None, then ensure failed UUID collection and logging use the correct object UUID; add or run the relevant failure-path tests if they exist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100