[Epic]: Bugs

[Chloeroumengas]

Why do we need this functionality?

X

What are we developing?

X

What are the validation criteria to validate this feature?

X

What's out of scope for this feature?

X

Should this feature be feature flagged?

• [ ] Feature Flagged

How are we going to code this feature?

X

Are there any technical decisions made that should be shared?

X

What is preventing us from delivering this feature?

X

What can the feature potentially break?

X

[dosubot[bot]]

🤖

Hello again, @Chloeroumengas! It's good to see you contributing to the Quivr repository. I hope you're doing well. Let's dive into this new issue you've raised.

Based on the provided context, it appears that the specific bugs being referred to in your request are not explicitly mentioned. The bug report template includes fields for you to describe what happened, provide relevant log output, and share your contact information, but it does not specify any particular bugs. You are expected to fill in the details of the bug you encountered. You can refer to the issue template for more details.

As for your questions about known workarounds, existing solutions or patches, and related bug reports or issues, I wasn't able to find any within the Quivr repository. It's possible that the information may be available elsewhere or I could have missed it.

Regarding the nature of the bugs, without specific details, it's challenging to determine if they are related to a specific feature or functionality of Quivr.

If you could provide more details about the bugs you're referring to, it would be easier to provide a more accurate response. This includes information like when the bug occurs, steps to reproduce it, expected vs. actual results, and any error messages or logs you might have.

As for the development, validation, and potential risks of this feature, without more specific information about the feature or the bugs it's addressing, it's difficult to provide a detailed plan or assessment.

I hope this helps, and I look forward to your response with more details.

Sources

• .github/ISSUE_TEMPLATE/EXTERNAL_ISSUE_TEMPLATE.yml

---

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.

[tholonia]

@dosu-bot I am also having this same issue. The install of Quivr was without errors, but I am getting errors whenever I try to upload any type of file. The log says:

2023-12-04 21:07:37 backend-core                    | 2023-12-05 00:07:37,947:INFO - HTTP Request: GET http://kong:8000/rest/v1/customers?select=email&email=eq.jeff.milton%40gmail.com "HTTP/1.1 500 Internal Server Error"
2023-12-04 21:07:37 backend-core                    | 2023-12-05 00:07:37,948 [INFO] models.databases.supabase.user_usage: None
2023-12-04 21:07:37 backend-core                    | 2023-12-05 00:07:37,948 [ERROR] models.databases.supabase.user_usage: Error while checking if user is a premium user
2023-12-04 21:07:37 backend-core                    | 2023-12-05 00:07:37,948 [ERROR] models.databases.supabase.user_usage: {'code': 'XX000', 'details': None, 'hint': None, 'message': 'called `Result::unwrap()` on an `Err` value: InvalidPosition'}

The issue appears to be related to "InvalidPosition" in Result::unwrap().

As far as I know, this app runs entirely in a docker container, so it appears this error is related to the install procedure or something in the Quivr code itself.

[github-actions[bot]]

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.