cwtch.im

/

cwtch

merging some bugfixes #163

Integrado

sarah integrou 1 cometimento(s) do ramo bigmerge no ramo master

2018-11-22 01:05:24 +00:00

erinn comentou

2018-11-22 00:48:41 +00:00

Proprietário(a)

we need to be able to set the AIF before launching individual peers, so this splits that out

we need to be able to set the AIF before launching individual peers, so this splits that out

buildbot comentou

2018-11-22 00:49:00 +00:00

Membro

Drone Build Status: failure

https://build.openprivacy.ca/cwtch.im/cwtch/278

Drone Build Status: failure https://build.openprivacy.ca/cwtch.im/cwtch/278

buildbot comentou

2018-11-22 01:03:26 +00:00

Membro

Drone Build Status: success

https://build.openprivacy.ca/cwtch.im/cwtch/280

Drone Build Status: success https://build.openprivacy.ca/cwtch.im/cwtch/280

sarah fechou este pedido de integração

2018-11-22 01:05:23 +00:00

dan comentou

2018-11-22 05:43:33 +00:00

Proprietário(a)

i did away with startPeer in app
Listen now does the go function thing, so you can call peer.Listen directly and itll fork

i did away with startPeer in app Listen now does the go function thing, so you can call peer.Listen directly and itll fork

dan comentou

2018-11-22 06:52:22 +00:00

Proprietário(a)

so yeah
lines 113-114

 		p.Init(app.mn)
 		p.Listen()

start and launch the peer. I got rid of app.startPeer cus its wrong and terrible

to be fair, LaunchPeers will basically nop
because
.Listen go calls .listenFn inside a look to handle socket fails
and you added cp.started = true inside listenFn
so LaunchPeers should always find them all started already

so yeah lines 113-114 ``` p.Init(app.mn) p.Listen() ``` start and launch the peer. I got rid of app.startPeer cus its wrong and terrible to be fair, LaunchPeers will basically nop because .Listen go calls .listenFn inside a look to handle socket fails and you added `cp.started = true` inside listenFn so LaunchPeers should always find them all `started` already

Inicie a sessão para participar neste diálogo.

Sem revisores

Sem rótulo

ready-for-implementation

Sem etapa

Sem encarregados

3 Participantes

Notificações

Data de vencimento

A data de vencimento é inválida ou está fora do intervalo permitido. Por favor, use o formato 'aaaa-mm-dd'.

Sem data de vencimento definida.

Dependências

Não estão definidas dependências.

Referência: cwtch.im/cwtch#163

Nenhuma descrição fornecida.