Skip to content
New issue

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

Issue with saving values #63

Open
alensiljak opened this issue Feb 13, 2025 · 3 comments
Open

Issue with saving values #63

alensiljak opened this issue Feb 13, 2025 · 3 comments

Comments

@alensiljak
Copy link
Contributor

alensiljak commented Feb 13, 2025

I am not too familiar with React but there seems to be a general issue with accepting and saving values entered into input boxes.

The case in point:
There is the new view for configuring Parsing Settings. I've set up both options - Vision and Document Model - with API keys and models.
While staying on the same page, I'm trying to upload a document. The message pops up that I need to configure these models. Clicking OK brings me back and all the fields have been reset to defaults, the API keys are gone.

This happens every time I come back to this view and try to upload a document.

Perhaps having an explicit Save button is not such a bad idea, after all. It makes changes explicit and allows for rolling back if one changes their mind before committing.

@alensiljak
Copy link
Contributor Author

Previously I've noticed an issue with typing the URL for Ollama in the Model Settings. I was trying to replace localhost with host.docker.internal, the URL required to connect to Ollama from a docker container in which Open Health is running.
For whatever reason, the value shown in the console, where the application is running, never got to the full URL. It was increasing character by character and then stopped at some point, as if rate-limited.
The end result was that the value in the text box was host.docker.internal but in the console something like host.docker.int.
Hence there were constant errors even though the UI was showing the correct value.
This looks like a scenario where the users are utterly confused by what is happening in the background.

@alensiljak
Copy link
Contributor Author

Now the main settings seem to be saved.
The settings in the Manage Sources are still not being stored. Or they get reset every time when the page is opened.

@FedAnt
Copy link

FedAnt commented Mar 3, 2025

log

app-1            | prisma:error 
app-1            | Invalid `prisma.user.findUniqueOrThrow()` invocation:
app-1            | 
app-1            | 
app-1            | An operation failed because it depends on one or more records that were required but not found. Expected a record, found none.
app-1            |  ⨯ Error [PrismaClientKnownRequestError]: 
app-1            | Invalid `prisma.user.findUniqueOrThrow()` invocation:
app-1            | 
app-1            | 
app-1            | An operation failed because it depends on one or more records that were required but not found. Expected a record, found none.
app-1            |     at async d (.next/server/app/page.js:1:5256) {
app-1            |   code: 'P2025',
app-1            |   clientVersion: '6.4.1',
app-1            |   meta: [Object],
app-1            |   digest: '2059938756'
app-1            | }

http://localhost:3000

Application error: a server-side exception has occurred (see the server logs for more information).
Digest: 2059938756

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants