-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fails to start for the first time due to 'datastore key does not have a valid format' #1615
Comments
Hey @lidel I see the problem. Basically, there should be a mismatch of versions for But let's fix this in the correct way! I will create a PR for |
@vasco-santos / @lidel can this be closed now? |
We just need interface-datastore#24 to get released and then update the |
Also bumping into this issue here: peer-base/peer-base#95 |
@pgte I believe @vasco-santos fixed this yesterday, to get the fix you need a fresh npm install of your modules |
In this case @pgte, since you are already updating In the meanwhile, if you do not upgrade those package versions, I think that it will work fine for you. |
As `instance of` fails using different versions of a module, it was changed to use `class-is`. Needs: - [x] [js-peer-id#84](libp2p/js-peer-id#84) - [x] [interface-datastore#24](ipfs/interface-datastore#24) Fixes #1615
Type: Bug
Severity: High-ish?
Description:
After switching from js-ipfs
0.31.7
to0.32.3
switching to embedded node in companion produces an error:What is interesting, is that if I switch to External node and then back again to Embedded one, second time js-ipfs tries to initialize is successful and everything works as expected.
I did not look into it deeper, but my guess is that there is some sort first-run init that happens after the error occurs that fixes datastore(?) and makes following runs in the same context to work fine. Maybe IPNS tries to publish key before it is stored or something?
cc @vasco-santos in case its something obvious
Steps to reproduce the error:
To build Companion with js-ipfs v0.32.3 and run in Firefox (but the same issue is in Chromium):
git clone https://github.com/ipfs-shipyard/ipfs-companion.git
cd ipfs-companion
git reset --hard 21eb92bee2b8ea99daa3fb1836431bd63f047c24
npm run dev-build
npm run firefox
Then, go to Preferences and switch to Embedded node. Initial try will fail, following ones will succeed.
The text was updated successfully, but these errors were encountered: