nextcloud / nextcloud/context_chat_backend

Chunk/context limit broken or too limited?

Open
#258 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug priority: normal
Dominant language
Python
Stars
27
Forks
24
Avg merge
3d 4h
Merged PRs (30d)
6

Description

Which version of Nextcloud are you using?

31

Which version of PHP context_chat are you using?

4.5.0

Which version of backend context_chat are you using?

4.5.0

Nextcloud deployment method?

docker-compose

Describe the Bug

I noticed with Context Chat that I have to give it very selective context for it to work as expected - as in pointing it at the exact subfolder (or one folder up from that) for it to find the file I'm asking about. If I query from higher than that, it seems to only include a subset of my data in the context, and thus doesn't find the file. I also see the following errors in the log and I'm not sure if these are related, but I'm guessing not.

decode: cannot decode batches with this context (calling encode() instead) init: embeddings required but some input tokens were not marked as outputs -> overriding

To Reproduce

Ask Context Chat a question about a file's contents from a higher folder level, aka, make it have to look through more data to find what you're asking about.

PHP logs (Warning these might contain sensitive information)

No response

Ex-App logs (Warning these might contain sensitive information)

No response

Server logs (if applicable)

No response

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the reported query in Context Chat from a higher folder level, using the versions and docker-compose deployment described in the issue. Inspect how much data is included in the context and whether the logged decode or embeddings warnings occur; done means the requested file can be found from the higher folder level or the limitation is clearly identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, php, python
Domain
ai, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.