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

[BUG] Brain are being deleted when user access brain management tab #1644

Closed
mamadoudicko opened this issue Nov 16, 2023 · 2 comments
Closed
Assignees
Labels
area: backend Related to backend functionality or under the /backend directory area: frontend Related to frontend functionality or under the /frontend directory Stale

Comments

@mamadoudicko
Copy link
Contributor

mamadoudicko commented Nov 16, 2023

  • Brains are being deleted in production if you click on them in the brain list.
  • If you go from people tabs to settings tab on a brain it starts to fliker like hell
@mamadoudicko mamadoudicko converted this from a draft issue Nov 16, 2023
@mamadoudicko mamadoudicko moved this from In Progress to To Be Validated in Quivr's Roadmap Nov 16, 2023
@dosubot dosubot bot added area: backend Related to backend functionality or under the /backend directory area: frontend Related to frontend functionality or under the /frontend directory labels Nov 16, 2023
Copy link

dosubot bot commented Nov 16, 2023

🤖

Hi @mamadoudicko, great to see you again!

Based on the provided context and the code in the repository, it's not true that brains are being deleted when a user accesses the brain management tab. The deletion of a brain only occurs when the delete/unsubscribe button is clicked, which triggers the handleUnsubscribeOrDeleteBrain function. This function is not automatically called when the brain management tab is accessed.

The Python function delete_brain_user takes in a user ID and a brain ID, and deletes the brain associated with those IDs. If the brain to be deleted is of type API, it also deletes any associated secrets. This further confirms that brains are not deleted simply by accessing the brain management tab, but only when the user actively chooses to delete a brain.

Here are the relevant sources:

If you're experiencing this issue, it might be due to a different part of the codebase or a specific set of circumstances that weren't covered in the provided context. Could you provide more details about the issue? For example, are there any error messages displayed when this issue occurs? Or could you provide the steps to reproduce this issue? This information could help identify the cause of the problem.

Sources


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.

@Chloeroumengas Chloeroumengas moved this from To Be Validated to Done in Quivr's Roadmap Dec 4, 2023
Copy link
Contributor

Thanks for your contributions, we'll be closing this issue as it has gone stale. Feel free to reopen if you'd like to continue the discussion.

@github-actions github-actions bot added the Stale label Dec 16, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: backend Related to backend functionality or under the /backend directory area: frontend Related to frontend functionality or under the /frontend directory Stale
Projects
None yet
Development

No branches or pull requests

2 participants