-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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]: Issue with yarn.lock #1739
Comments
🤖 Hello @mxhp75, I'm Dosu, an AI bot here to assist you with your issues regarding Quivr while we wait for a human maintainer. I can help you troubleshoot bugs, answer your queries, and guide you to become a contributor. Let's work together to solve this problem! Based on the error log you've provided, it seems like the issue is related to a network connection problem during the Here are a few steps you can take to troubleshoot this issue:
# Delete the yarn.lock file
rm yarn.lock
# Install the dependencies again
yarn install
Remember to rebuild your Docker image after making these changes. In addition, I found a few similar issues in the Quivr repository that might be helpful:
I hope this helps! If you have any other questions or if the issue persists, please let me know. Sources |
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. |
What happened?
After running
docker compose -f docker-compose.yml up --build
there was a front end error.Attempting to run quivr locally on an ubuntu machine.
Relevant log output
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: