We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
So I've tried giving llama2 a couple of documents, and I always seem to get no suggested tags.
Am I missing a set of possible tags it can choose from? (I assume this process can be better than the current paperless machine learning).
The text was updated successfully, but these errors were encountered:
Hi @psyciknz , can you run the container with LOG_LEVEL: 'debug' in the environment variables and then provide the logs?
LOG_LEVEL: 'debug'
Sorry, something went wrong.
I had that set. Ran it today (pulled new) and it managed to read from paperless. I wonder if there was some dns caching issue internally.
It is finding something now which is good. But I note in teh logging that when you hit the refresh documents, no log messages appear.
time="2024-11-28T23:55:23Z" level=debug msg="No documents with tag paperless-gpt-auto found" [GIN] 2024/11/28 - 23:55:26 | 200 | 529.285667ms | 192.168.10.147 | GET "/api/documents" time="2024-11-28T23:55:33Z" level=debug msg="No documents with tag paperless-gpt-auto found" [GIN] 2024/11/28 - 23:55:37 | 200 | 772.981616ms | 192.168.10.147 | GET "/api/documents" time="2024-11-28T23:55:44Z" level=debug msg="No documents with tag paperless-gpt-auto found"
I think the /api/documents is it hitting the paperless api
Here is the result of the document suggesting tags.
No branches or pull requests
So I've tried giving llama2 a couple of documents, and I always seem to get no suggested tags.
Am I missing a set of possible tags it can choose from? (I assume this process can be better than the current paperless machine learning).
The text was updated successfully, but these errors were encountered: