nextcloud / nextcloud/context_chat_backend
[feat]: Return user-facing errors to taskproc where it makes sense
Open
Nobody has claimed this yet.
enhancement
priority: medium
- Dominant language
- Python
- Stars
- 27
- Forks
- 24
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 6
Description
See https://github.com/nextcloud/integration_openai/issues/296
Although changes in nc_py_api might be required.
Cases where this would make sense:
- when no docs are found for a scoped query: https://github.com/nextcloud/context_chat_backend/blob/0d3308f315736c5214701012f8573551abbb6412/context_chat_backend/task_fetcher.py#L546-L548
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 with the linked integration_openai issue and the scoped-query handling in context_chat_backend/task_fetcher.py at lines 546-548. Check how taskproc currently reports failures and whether the related nc_py_api changes are required. Done means the no-documents case, and other justified cases, produce user-facing errors in taskproc.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100