Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: <https://github.com/issues?q=is%3Aissue user%3Aatom>
  • Checked that there is not already an Pulsar package that provides the described functionality: https://atom.io/packages

Description

A notification shows that Pulsar could not connect to IndexedDB

Steps to Reproduce

1. Open a version of Pulsar
2. Open a different version of Pulsar

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

At undefined

Error: Could not connect to indexedDB
    at IDBOpenDBRequest.dbOpenRequest.onerror (/home/mauricio/projects/pulsar_repos/pulsar/src/state-store.js:31:20)

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