-
-
Notifications
You must be signed in to change notification settings - Fork 136
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
Could not connect to indexedDB #531
Comments
I'm very much in favor of continuing the sqlite experiment. It would make it much less painful to run two versions of Pulsar side-by-side. |
I have just hit this issue after updating to 1.112 from 1.105, it delays pulsar starting |
@mramendi This should only happen when two instances of Pulsar are running at the same time. |
Tried again, issue did not reproduce. So yes, probably something related to the update, where I hit another bug #544 and had to uninstall and reinstall. |
I had apparently the same error once after upgrading to the 1.119.0: VersionsPulsar: 1.119.0 x64 Stack TraceCould not connect to indexedDB
Commands
Non-Core Packages
Additional Information |
Prerequisites
Description
A notification shows that Pulsar could not connect to IndexedDB
Steps to Reproduce
Expected behavior:
Not have this notification
Versions
Pulsar: 1.104.0-dev x64
Electron: 12.2.3
OS: Ubuntu 20.04.6
Thrown From: Pulsar Core
Stack Trace
Could not connect to indexedDB
Fix
There's no "easy fix" - basically, the way Pulsar keeps track of states is with IndexedDB, which is a horrible, horrible. Two Electron apps with the same name will conflict and it's hard to make backups, it's hard to inspect, etc.
There is a solution that I can pitch, that is, to move all IndexedDB storage to SQLite3. I made some experiments with SQLite3, and it seems that this could work - now we only need to decide if we want to follow up with this experiment
The text was updated successfully, but these errors were encountered: