nextcloud / nextcloud/context_chat_backend
[install-help]: The initial indexing is still running.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 27
- Forks
- 24
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 6
Description
NexcCloud AIO 33.0.5
context_chat_backend 5.3.0
HARP
Describe the issue
The Docker container is there and is communicating to the appAPI but saying
The initial indexing is still running
Documents in vector database 122 (0 sent)
The stat command says
docker exec --user www-data -it nextcloud-aio-nextcloud php occ context_chat:stats
ContextChat statistics:
The indexing is not complete yet.
Total eligible files: 218
Files in indexing queue: 219
New files in indexing queue (without updates): 219
Queued documents (without files):array (
)
Files successfully sent to backend: 0
Indexed documents: array (
'files__default' => 122,
)
Actions in queue: 0
File system events in queue: 0
When I run
docker exec -u www-data nextcloud-aio-nextcloud php occ background-job:worker -t 60 'OC\TaskProcessing\SynchronousBackgroundJob'
It runs but nothing seems to happen
I did run docker exec --user www-data -it nextcloud-aio-nextcloud php occ context_chat:scan admin
and that is how that first 122 show up
But how to get it too complete or maybe its not doing the embedbing
Any ideas ?
Thanks
Screenshots
If applicable, add screenshots to help explain your problem.
Server logs (if applicable)
Context Chat Backend logs (if applicable, from the docker container)
init: embeddings required but some input tokens were not marked as outputs -> overriding
decode: cannot decode batches with this context (calling encode() instead)
init: embeddings required but some input tokens were not marked as outputs -> overriding
decode: cannot decode batches with this context (calling encode() instead)
init: embeddings required but some input tokens were not marked as outputs -> overriding
llama_perf_context_print: load time = 113.30 ms
llama_perf_context_print: prompt eval time = 482.88 ms / 96 tokens ( 5.03 ms per token, 198.81 tokens per second)
llama_perf_context_print: eval time = 0.00 ms / 1 runs ( 0.00 ms per token, inf tokens per second)
llama_perf_context_print: total time = 491.20 ms / 97 tokens
Setup Details (please complete the following information):
- Nextcloud Version: [eg. 28.0.1, master]
- AppAPI Version: [eg. 2.0.1]
- Context Chat PHP Version [e.g. 1.0.0]
- Context Chat Backend Version [e.g. 1.0.0]
- Nextcloud deployment method: [eg. Apache bare-metal]
- Context Chat Backend deployment method: [eg. manual, one-click]
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 reproducing the reported state with the provided context_chat:stats, context_chat:scan admin, and background-job worker commands. Read the Context Chat Backend logs alongside the queue counts, especially the 219 queued files and zero successfully sent files. Done means identifying why indexing does not progress and documenting or verifying the resulting fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- ai, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100