Improve error message returned when attempting to resolve did:dht DID that hasn't yet been published. Currently a bit misleading.

[mistermoe]

Hitting the following error when attempting to resolve did:dht DIDs:

code:

const did = await DidDhtMethod.create();
const didResolutionResult = await DidDhtMethod.resolve({ didUrl: did.did });

error:

Error: Invalid SignedPacket bytes length, expected at least 72 bytes but got: 25
  at SignedPacket.fromBytes (file:///Users/moe/code/tbd/ose/web5/node_modules/pkarr/lib/signed_packet.js:75:13)
  at Pkarr.relayGet (file:///Users/moe/code/tbd/ose/web5/node_modules/pkarr/index.js:46:25)

---

Update

After talking to @decentralgabe , realized that this was happening because the DID hadn't yet been published. publishing requires passing publish: true to DidDhtMetod.create and waiting for ~10s. Better error message and some documentation could be helpful (though not clear where we should put those docs cc: @angiejones @ALRubinger @leordev)

[decentralgabe]

This is a result of attempting to fetch the DID before it has published, which takes about 10 seconds. The error can be better but I wouldn't classify it as a bug.

[mistermoe]

kk thanks! this works:

const sleep = (time) => new Promise(resolve => setTimeout(resolve, time));

const did = await DidDhtMethod.create({ publish: true });

await sleep(10_000);
const didResolutionResult = await DidDhtMethod.resolve({ didUrl: did.did });

agree that it's not a bug and agree that the error message could be better. removed the bug label and updated the github issue description to reflect