<davkal> for proper contribution, you’d need to fork the scope repo and open a PR
dannn
yep okay standard procedure
koolhead17 has quit
ofthecure joined the channel
koolhead17 joined the channel
dpw has quit
dpw joined the channel
dannn has quit
moonfish has quit
koolhead17 joined the channel
arunpyasi joined the channel
moonfish joined the channel
arunpyasi joined the channel
arunpyasi joined the channel
koolhead17 joined the channel
koolhead17 has quit
koolhead17 joined the channel
seti_k has quit
Spanktar joined the channel
errordeveloper joined the channel
dpw has quit
moonfish has quit
trifygri joined the channel
errordeveloper joined the channel
trifygri has quit
ofthecure has quit
ofthecure joined the channel
errordeveloper joined the channel
koolhead17 has quit
errordeveloper joined the channel
koolhead17 joined the channel
koolhead17 has quit
Brennan joined the channel
Brennan
Hi all, I'm seeing an issue with the following signature: We have Weave nodes A, B, and C, where B and C are inside the same network. Once node B connects to A (with status "established"), C cannot connect to A (gets stuck in "pending" status). Other nodes from outside B&C's network can still connect successfully. If B disconnects, there's a 2 minu
te cooling off period, after which C is able to connect (but B is not).
moonfish joined the channel
ofthecure has quit
weave-slack-bot
<monadic> brennan, alexis here from weave. would you mind posting this question to the weave-users google group please? quite a few of our team are offline right now, and I’d like to make sure your question is seen in the next 6-12 hours