Right now the docs correspond to what's on master. We need docs for each daemon release so developers can see what's available in the version they are using.

https://github.com/jimporter/mike may be helpful.

After shutdown, lnd logs "Shutdown complete" without a trailing newline. Upon restart, the line continues:

2019-12-05 22:39:18.593 [INF] LTND: Shutdown complete2019-12-05 22:39:39.821 [INF] LTND: Version: 0.8.2-beta commit=v0.8.0-beta-386-gf3398c0c0ecc469c31e1f7e18e0fa2d63b5729ed, build=production, logging=default

On macOS, it's a fairly standard practice to display a pre-roll if your application needs some form of permissions, before calling the system APIs for the first time that will actually produce the system's requested-permissions window.

For instance, for any given end-user, the following window is likely A) intimidating, and B) possibly encourages insecure habits, such as simply clicking "acce

Now that we have code coverage enabled there are a few places we can easily improve test coverage for.

• Get/Set all parameters for all types of objects
• Trigger the Settings updated code path by setting a registry key
• Test out multiple registration execution modes
• Test Server IP load balancing mode
• Packet drops in validating received initial token
• Trace ru

When stateless retries are enabled, Quinn embeds some state in the retry token and authenticates it with a HMAC. This information is not secret, so the current approach works, but it would be more in the spirit of QUIC to use strong encryption to prevent other parties from coming to rely on that data, creating a stability hazard.

The stateless nature of retry tokens requires some care if we wan

protocol SomeProtocol {
    init<T>(t: T)
}

The code generated by the protocol above will have an initializer like below which cause a compiler error.

     required init(t: T) {
        
    }

It looks like the type placeholder is missing when generating for an initializer.

Filling from mobile so we don't forget. Good first issue if someone wants to fix this via a PR before I get to it next week.

Right now, when IPFS integrations are disabled via a toggle, extension assumes http://.

Most servers redirect http:// → https://, or have HSTS set up, but Companion should default to https://, because if someone did not set up redirect to a secure context,