Giters

QuivrHQ / quivr

Your GenAI Second Brain 🧠 A personal productivity assistant (RAG) ⚡️🤖 Chat with your docs (PDF, CSV, ...) & apps using Langchain, GPT 3.5 / 4 turbo, Private, Anthropic, VertexAI, Ollama, LLMs, Groq that you can share with users ! Local & Private alternative to OpenAI GPTs & ChatGPT powered by retrieval-augmented generation.

Home Page:https://quivr.app

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[Bug]: Can't add new Brain -- UI doesn't display brain choice

Croccodoyle opened this issue · comments

commented

What happened?

No choice of brain available on Chrome Version 122.0.6261.112 (Official Build) (arm64) or Safari Version 17.3.1 (19617.2.4.11.12).... Running on Sonoma 14.3.1
Screenshot 2024-03-08 at 18 01 37

Relevant log output

i18next: languageChanged en
4884-fc0a6fc783565dbd.js:1 i18next: initialized Object
:5050/user:1 
        
        
       Failed to load resource: the server responded with a status of 403 (Forbidden)
_vercel/insights/script.js:1 
        
        
       Failed to load resource: the server responded with a status of 404 (Not Found)
:3000/:1 Refused to execute script from 'http://localhost:3000/_vercel/insights/script.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
:5050/user:1 
        
        
       Failed to load resource: the server responded with a status of 403 (Forbidden)
:5050/user:1 
        
        
       Failed to load resource: the server responded with a status of 403 (Forbidden)
:5050/user:1 
        
        
       Failed to load resource: the server responded with a status of 403 (Forbidden)
1250-f2578602441d42c3.js:1 No analytics found

Twitter / LinkedIn details

No response

commented

Hey there, @Croccodoyle! Great to see you diving into the depths of quivr again. What's cooking in your Brain kitchen today? 🧠🍳

Based on the error logs you've provided, it seems like there might be an issue with the server's authorization process. The 403 (Forbidden) status code typically indicates that the server understands the request but refuses to authorize it. This could be due to a few reasons:

  1. Authentication/Authorization Issue: The user account used for login might not have the correct roles or permissions, or the login process did not complete successfully. This could be due to changes in the authentication flow or issues with session management.

  2. Frontend-Backend Contract Violation: If there have been recent changes to the backend API that the frontend relies on (for example, changes in the API endpoint, request payload, or required headers for the "add brain" functionality), and the frontend has not been updated accordingly, this could lead to a 403 response.

  3. CORS Policy: While less likely to directly cause a 403 error, if there are Cross-Origin Resource Sharing (CORS) policy misconfigurations, it could potentially lead to issues with requests being blocked or failing in unexpected ways.

  4. Browser-Specific Issues: Since you mentioned this issue occurs on both Chrome and Safari, it's less likely to be a browser-specific issue and more likely related to the application's code or server configuration.

Given the context and the nature of the error, the first step should be to verify the user's permissions and ensure that the login process is completing successfully with the correct session information. Following that, reviewing any recent changes to the backend API and ensuring the frontend is aligned with those changes would be crucial. Lastly, checking the browser console for additional errors and reviewing the network requests for failed requests can provide more insight into the issue.

As for the expected behavior of the "Add New Brain" functionality, it should present the user with a form to input a "Brain name" and "Description", set the visibility of the brain to either "Private" or "Public", and provide confirmation messages upon successful creation or error during the creation process. It also allows for the configuration of brain parameters, inviting new users to the brain, and managing the brain's visibility status. This is based on the localization keys and values provided in the frontend/public/locales/en/brain.json file.

I hope this helps in identifying the potential causes of the issue. If you need further assistance, please provide more details about the steps you took before encountering the error, any changes made to the codebase or server configuration, and any additional error messages or logs.

Sources

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.