志宇
志宇
`SSH` in capitals is rather odd in my opinion. Is this a specific request from Brandon? Why aren't we naming it `dmsg-ssh` or `skyssh`?
Note that we are handling `dmsg` communication via the `snet.Network` structure.
> @evanlinjin note that uptime only requires the time elapsed since the last connection to the discovery (ap4y suggested implementing uptime tracking in transport discvory). The total uptime is calculated...
Looking at the logs, I see: `panic: send on closed channel` -> A quick hack is to use `sync.Mutex` to ensure close/write actions do not overlap. Of cause, if there...
Is this done?
@nkryuchkov please postpone this PR until I have finished integrating new dmsg with skywire.
@jdknives 1. We need a way for `Responder` to inform `Initiator` that it accepts the request. 2. Given the assumption that `Responder` will always agree to establish the transport, the...
I like this. But I would rename `RuleOfType` to `RulesOfType`. Also, let's have both `NotExpired()` and `Expired()`.
Logs of `A` before restart of `B`: ``` [2019-05-10T16:59:48+12:00] INFO [chat.v1.0]: 2019/05/10 16:59:48 received and trashed: {"message":"Hello Joe!","sender":"031b80cd5773143a39d940dc0710b93dcccc262a85108018a7a95ab9af734f8055"} [2019-05-10T16:59:48+12:00] INFO [router]: Forwarded packet to App on Port 1 [2019-05-10T16:59:48+12:00] INFO...
Logs of `B` when restarting `B`: ``` [2019-05-10T17:00:38+12:00] WARN [trmanager]: Failed to change transport status: status: 401, error: {"error":{"message":"SW-Nonce does not match","code":401}} ``` Hence, this issue may be related to...