manifest is not defined
vincentux opened this issue ยท 6 comments
After I entered my secret file,
I have the following message:
ReferenceError: manifest is not defined
- Xubuntu
- Firefox 72.0.1
- Patchfox 2020.2.1
I also ran into this yesterday, using the latest version of patchwork.
The manifest.json has a manifest: async
though and I can run sbotcli call manifest
to get it...? ๐ฌ๐คทโโ๏ธ
cc @christianbundy since I think this is used in oasis, too?
Okay, this is not actually about the RPC command. I used a local dev build to get the sourcemap and tracked it down to here:
I don't see a (re-)definiton of manifest
anywhere in that file. I think it was a configuration value in a previous version?
If I paste in a copy of my ~/.ssb/manifest.json
like this it works:
diff --git a/src/packages/settings/IdentityAndConnection.svelte b/src/packages/settings/IdentityAndConnection.svelte
index 9ed92b4..e8629f9 100644
--- a/src/packages/settings/IdentityAndConnection.svelte
+++ b/src/packages/settings/IdentityAndConnection.svelte
@@ -8,6 +8,7 @@
let remote = "";
document.title = "Patchfox - Settings - Identity And Connection";
+ let manifest = `{"auth":"async","address":"sync","manifest":"sync","multiserver":{"parse":"sync","address":"sync"},"multiserverNet":{},"get":"async","createFeedStream":"source","createLogStream":"source","messagesByType":"source","createHistoryStream":"source","createUserStream":"source","createWriteStream":"sink","links":"source","add":"async","publish":"async","getAddress":"sync","getLatest":"async","latest":"source","latestSequence":"async","whoami":"sync","progress":"sync","status":"sync","getVectorClock":"async","version":"sync","seq":"async","usage":"sync","clock":"async","plugins":{"install":"source","uninstall":"source","enable":"async","disable":"async"},"gossip":{"add":"sync","remove":"sync","connect":"async","disconnect":"async","changes":"source","reconnect":"sync","disable":"sync","enable":"sync","ping":"duplex","get":"sync","peers":"sync"},"replicate":{"changes":"source","upto":"source","request":"sync","block":"sync"},"friends":{"hopStream":"source","onEdge":"sync","isFollowing":"async","isBlocking":"async","hops":"async","get":"async","createFriendStream":"source","stream":"source"},"blobs":{"get":"source","getSlice":"source","add":"sink","rm":"async","ls":"source","has":"async","size":"async","meta":"async","want":"async","push":"async","changes":"source","createWants":"source"},"invite":{"create":"async","accept":"async","use":"async"},"query":{"read":"source","explain":"sync"},"ws":{},"ebt":{"replicate":"duplex","request":"sync","block":"sync","peerStatus":"sync"},"ooo":{"stream":"duplex","get":"async"},"links2":{"read":"source"}}`
const saveConfiguration = ev => {
setConnectionConfiguration({remote, keys: JSON.parse(keys), manifest});
location.reload();
okay, i also found src/core/platforms/ssb/manifest.js
so I think this is an relict that can be removed altogetehr.
Same problem here.
Windows 7
Firefox 72.0.2
I have a fixed version here, will release today.
this has been fixed.