nextcloud / nextcloud/context_chat
flaky integration tests
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 29
- Forks
- 12
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 5
Description
integration tests in this repo and in the backend fail randomly, the cause seems to be related to the model download from hf.
rate-limiting is one of the causes (which we can solve like llm2 does, with local caching),
the other issue is that /init and /enable are completed while the model file does not seem to be in place fully, so in a race condition, the embedding process sometimes finds the file, sometimes doesn't:
https://github.com/nextcloud/context_chat/actions/runs/33515757237/job/99882236764#step:33:46
and in yet another case, seems to crash due to OOM?
https://github.com/nextcloud/context_chat/actions/runs/33515757237/job/99882236566#step:34:20
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 integration tests and the two linked GitHub Actions job logs. Trace the model download around /init and /enable, including rate limiting, incomplete files, and the reported OOM case. Done means the integration tests no longer fail randomly for these documented download and initialization scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- huggingface, php
- Domain
- machine-learning, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100