oasis Error: could not connect to sbot #6
Comments
|
Looks like this might happen when indexes are behind. |
|
I'm seeing the same error as above consistently with a pre-launched Any known workaround? This is with oasis and ssb-server installed via There are no additional plugins enabled in my |
|
I think this is actually just happening when your indexes are behind. Could you run {
"progress": {
"indexes": {
"start": 707179111,
"current": 707179111,
"target": 707179111
}
},
"sync": {
"since": 707179111,
"plugins": {
"last": 707179111,
"keys": 707179111,
"clock": 707179111,
"time": 707179111,
"feed": 707179111,
"backlinks--oaWWDs8g": 707179111,
"private--oaWWDs8g": 707179111,
"query": 707179111,
"search": 707179111,
"tags": 707179111,
"patchwork-subscriptions": 707179111,
"patchwork-channels": 707179111,
"patchwork-contacts": 707179111
},
"sync": true
},
} |
|
Thank you for your help. This is a ssb-server with a very small number of follows. Index seems to be fully up to date: Upon closer reading of this issue, I realize I may be encountering a different problem. The error I am seeing is not on startup, but rather when I hit any endpoint except The keys mentioned are FWIW, I'm able to interact with the same server using |
|
Oh, totally different issue. I think I've fixed this in the 15.0.1 upgrade, could you confirm that the fix resolves this bug for you? |
|
@christianbundy -- I couldn't find a 15.0.1 but did try oasis 1.15.1. The symptom with this version seems to be the same. This is the line where the exception is being raised: From a glance it wasn't clear whether Looks like something is amiss with |
|
This is the output of Adding explicit |
|
Are you seeing this bug when running from an external ssb-server or with only oasis running its own server? I see the sbot plugins.install ssb-backlinks
sbot plugins.enable ssb-backlinksYou'll have to restart your ssb-server, and if you run into an "Error: expected X but had Y" you may have to use this fix. |
|
I can consistently reproduce this behavior with both internal and external server. Interestingly, patchfoo and npmRegistry are showing up in Here's a bit more context from the running oasis instance to show that it has been started with the internal server: Here's the full process listing of the container running oasis. And the full list of listening connections, When the patchfoo plugin is enabled, |
|
Found the bug, could you replace I really wish upstream dependencies weren't parsing our CLI options, that's why I had to use |
|
Actually, I just published a new version that I'm hoping will resolve this and your other issue. I've hidden the CLI options from upstream modules so they can't attach their own semantics to them. :~) |
|
Thank you @christianbundy -- the latest version appears to have fixed my issues! Also, after a bit of fiddling with ssb-server and my config, oasis is working well with both the internal and external server. |
|
Woo, thanks for the confirmation! |
…t-info-2.8.9 Bump hosted-git-info from 2.8.8 to 2.8.9
Seems like this only happens the first time you start the server?
The text was updated successfully, but these errors were encountered: