Closed georgeowell closed 4 years ago
See if you open your ~/.ssb/config
file? Is the JSON in there malformed?
You can run it through this thing to check: https://jsonlint.com/
See if you open your
~/.ssb/config
file? Is the JSON in there malformed?You can run it through this thing to check: https://jsonlint.com/
There was actually a comma missing in there which I have now corrected. Doesn't seem to have made any difference to the original problem though :disappointed:
This is what ~/.ssb/config
looks like now:
{
"friends": {
"hops": 2
},
} "friendPub": {
"hops": 3
},
"gossip": {
"friends": true,
"global": true
}
}
Should I try emptying that file?
Interesting! So I just did that and it worked!
The sbot log was a good hint:
sbot server
undefined:5
} "friendPub": {
^
When I take out the new friendPub
setting, everything works as usual. This is is my ~/.ssb/config
now:
{
"friends": {
"hops": 2
},
"gossip": {
"friends": true,
"global": true
}
}
Could someone else test if this happens for them if they mess with the pub privacy slider in Patchbay?
@georgeowell - i wasn't able to reproduce it by doing that.
@mixmix - has the 'ahoy' screen always prevented you from launching the app if you accidentally malform your config? or was there a release that didn't happen with?
wondering if you mouse slipped after clicking 'edit config' or something, haha
I remember madding ahoy not save config if it says malformed, not sure if it blocks you from launching. Might need to check that logic.
On Fri, 7 Jun 2019, 18:56 Gordon Martin, notifications@github.com wrote:
@georgeowell https://github.com/georgeowell - i wasn't able to reproduce it by doing that.
@mixmix https://github.com/mixmix - has the 'ahoy' screen always prevented you from launching the app if you accidentally malform your config? or was there a release that didn't happen with?
wondering if you mouse slipped after clicking 'edit config' or something, haha
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ssbc/patchbay/issues/344?email_source=notifications&email_token=AAUK3HVKZC727PUR4DFMGTDPZIBABA5CNFSM4HSNM2LKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXFAKDA#issuecomment-499778828, or mute the thread https://github.com/notifications/unsubscribe-auth/AAUK3HRFJKQU3KJRVCUZFJ3PZIBABANCNFSM4HSNM2LA .
This is what
~/.ssb/config
looks like now:{ "friends": { "hops": 2 }, } "friendPub": { "hops": 3 }, "gossip": { "friends": true, "global": true } }
Emm, the curly bracket before "friendPub"
signals the end of data. So this file is syntactically incorrect. Is it just me seeing this?
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
Operating system: Ubuntu 18.04 (GNOME 3)
After updating Patchbay to patchbay-Linux-8.0.1-x86_64 via AppImage (from Patchbay-linux-7.15.1-x86_64), I launched Patchbay and interacted with Ahoy and then was able to access the Scuttleverse as expected.
The next time I opened Patchbay, I was greeted by the Ahoy labelled window that was totally blank (white) which seemed to have hung. Nothing happened, even after five minutes so I closed Patchbay.
Now neither Patchbay or Patchwork (Patchwork-3.11.6-linux-x86_64) will launch or any older versions I try. When I launch any of these AppImages using the terminal, I get the following errors:
patchbay-Linux-8.0.1-x86_64
Patchbay-linux-7.15.1-x86_64
Patchwork-3.11.6-linux-x86_64
sbot 0.0.3
Anyone got any debugging advice? Looks like some sort of issue with Ahoy. Currently unable to access SSB at all :cry:
Opened an issue on Patchwork tracker also as it effects it: https://github.com/ssbc/patchwork/issues/1071