bloop: 0.5.4 stuck on loading and doesn't open
Describe the bug
A clear and concise description of what the bug is. If appropriate add a frontend
or backend
label.
The app is stuck on loading when starting.
Expected behavior What did you expect to happen?
The app should open
To Reproduce How can we reproduce the bug? Helpful information could include:
- MBP 13" Intel i5 2020
Screenshots or output
If applicable, add screenshots to help illustrate the bug.
Additional context Add any other context about the problem here.
About this issue
- Original URL
- State: closed
- Created 9 months ago
- Comments: 20 (7 by maintainers)
For reference, I was able to get around this by deleting the ai.bloop.bloop/qdrant folder in Application Support on Mac. After deleting, the app launched just fine. Interestingly, my experience was that I was on 0.5.6 which was working fine for a while and then suddenly the app wouldn’t get past the loading screen. Looks like I lost my conversation history by deleting the folder.
wow!!! it just works!!! awesome!!!
Method 1: Using Finder Open Finder: Click on the Finder icon in the Dock.
Go to Folder: From the menu bar at the top of the screen, select “Go” and then choose “Go to Folder” from the dropdown.
Type Path: In the “Go to the folder” dialog that appears, type ~/Library/Application Support/ai.bloop.bloop/qdrant and click on “Go”.
Method 2: Using Terminal Open Terminal: You can find it in the Applications folder under Utilities, or you can search for it using Spotlight (press Command + Space and type “Terminal”).
Navigate to Directory: Type the following command and press Enter to navigate to the target folder:
cd ~/Library/Application\ Support/ai.bloop.bloop/qdrant
Hey @yehiaabdelm can you download the
x86_64-apple-darwin-app
artefact from here:https://github.com/BloopAI/bloop/actions/runs/6472146134? Unzip it and install the dmg inIt is a version of bloop with extra initialisation logging (where bloop fails for you): https://github.com/BloopAI/bloop/pull/1036dmg/
.Once you’ve installed it, can you try and run it, and post the resulting logs to this thread? This would really help us narrow this problem down!