You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per my config, I am just using my datastore plugin. My datastore plugin is intentionally read-only, since it is a bridge to another interface that allows content-addressed reads, and only of sha-1 hashes.
$ GOLOG_LOG_LEVEL="swh-bridge=debug" IPFS_PATH=(mktemp -d) ./result/bin/ipfs init -e -p swhbridge
generating ED25519 keypair...done
peer identity: 12D3KooWHxWwyzX1aZB433nTyEGdbqFWsyr4ZSahvuye7YwsxoBy
initializing IPFS node at /tmp/tmp.zQqqP2vNm7
2022-07-28T21:02:29.611-0400 DEBUG swh-bridge bridge/datastore.go:160 Requested key bridge can't get: Data was a multihash encoded with 18, but expected 17 (SHA1)
Error: merkledag: not found
As one can see my datastore rejects a get request as impossible to translate. And then the command fails with Error: merkledag: not found. However (1), the local data seems initialized perfectly fine after all, at least I have used it without issue. So whatever failed here seems...not important?
I am normally a "fail fast" sort of person, but if I can in fact initialize a local node without doing any datastore read/writes (which seems like a reasonable thing to be able to do, all things equal), could this work more gracefully? Maybe with a --no-use-datastore flag to opt into non trying to the main version can stay fail fast?
Note I am already using -e / --empty-repo so it should not failing trying to download the read me. Of course I would expect it to fail (and that would be good) if it were! :)
The text was updated successfully, but these errors were encountered:
@Ericson2314 we think it's the empty MFS root,
and the MFS is incompatible over sha1-readonly datastore anyway.
So it's an incompatible feature that report it self poorly, it's not preventing other features from working.
Imo the only good simple solution here is making the log message better,
but that P4 since it require a pretty obscure setup to begin with, if you want to send a PR I'm gonna take a look at it.
Checklist
Installation method
built from source
Version
Config
Description
Per my config, I am just using my datastore plugin. My datastore plugin is intentionally read-only, since it is a bridge to another interface that allows content-addressed reads, and only of sha-1 hashes.
As one can see my datastore rejects a get request as impossible to translate. And then the command fails with
Error: merkledag: not found
. However (1), the local data seems initialized perfectly fine after all, at least I have used it without issue. So whatever failed here seems...not important?I am normally a "fail fast" sort of person, but if I can in fact initialize a local node without doing any datastore read/writes (which seems like a reasonable thing to be able to do, all things equal), could this work more gracefully? Maybe with a
--no-use-datastore
flag to opt into non trying to the main version can stay fail fast?Note I am already using
-e
/--empty-repo
so it should not failing trying to download the read me. Of course I would expect it to fail (and that would be good) if it were! :)The text was updated successfully, but these errors were encountered: