test(backend): skip failing tests

[mamadoudicko]

The objective of this PR is to guarantee the successful execution of backend CI tests. Our current challenge involves a growing count of test failures. This is compounded by instances where a single test failure goes unnoticed, subsequently triggering more test failures down the line. To address this issue, we need to enhance our CI monitoring and maintenance practices. It's crucial to emphasize that, moving forward, any CI test failures are likely to be significant and indicative of underlying problems requiring resolution.

Furthermore, it's important to note that adding skip instructions directly to the codebase should be avoided. Such instructions can obscure genuine issues and prevent the identification of actual problems within the code.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 25, 2023 9:24am
quivrapp	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 25, 2023 9:24am

[github-actions]

Risk Level 2 - /home/runner/work/quivr/quivr/backend/models/files.py

The changes in this file involve calling methods on supabase_db which is assumed to be a database object. The risk here is that these methods might not exist on the supabase_db object or they might not behave as expected. It would be good to ensure that these methods are properly defined and tested. For example, the link_file_to_brain() method now calls create_brain_vector() on supabase_db. Make sure this method exists and works as expected.

---

Risk Level 2 - /home/runner/work/quivr/quivr/backend/routes/chat_routes.py

The changes in this file involve modifying the default values for the model, temperature, and max_tokens parameters in the create_stream_question_handler function. These changes could potentially affect the behavior of the chatbot, but without knowing the specific use case, it's hard to say whether these changes are appropriate or not. It would be a good idea to thoroughly test these changes to ensure they don't introduce any unexpected behavior.

---

Risk Level 3 - /home/runner/work/quivr/quivr/backend/llm/qa_base.py

The changes in this file involve adding type ignore comments and making several changes to the way the code interacts with the vector store and the qa object. These changes could potentially cause issues if the ignored types cause unexpected behavior or if the changes to the vector store and qa object interactions are not handled correctly. Consider adding checks to ensure the types are as expected and thoroughly testing the new interactions with the vector store and qa object.

---

🔍🐞🧪

---

Powered by Code Review GPT

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ AttributeError: 'dict' object has no attribute 'user_id' /chat/{chat_id}/question/stream View Issue
• ‼️ AttributeError: 'dict' object has no attribute 'user_id' /upload View Issue
• ‼️ AttributeError: 'dict' object has no attribute 'user_id' /user/identity View Issue
• ‼️ TypeError: write() argument must be str, not None /crawl View Issue
• ‼️ IndexError: list index out of range /chat/{chat_id}/question/stream View Issue

_{Did you find this useful? React with a 👍 or 👎}