Richard Whitehouse

I dug into this - it's caused by https://github.com/rust-lang/cargo/issues/3530

`cargo install --git https://github.com/slerpyyy/cargo-count --branch master` works as a one liner.

> Similarly, for: > > ``` > parameter: > in: cookie > name: 'myParam' > style: 'form' > schema: > type: number > ``` > > I encode my parameter...

Surely `#[serde(default_value = 0.1)]` is better - and then any expression can be provided? In fact, that can replace any of the current usage right?

Hmm, I agree the later approach is likely preferable - although the former is likely to be much simpler (and the call graph analysis will need to consider platform triples...

Ah, I assumed that cargo audit used the cargo crate to gather the information from Cargo.

Yes, plan is to take https://github.com/Metaswitch/swagger-rs/pull/158/files at the point we take `hyper 1.x`, or push a fix to `hyper-old-types` which doesn't depend on `time 0.1`.

Do you mean the signup key? Is there any reason you can't follow the process in http://clearwater.readthedocs.io/en/stable/Clearwater_Configuration_Options_Reference.html to change the signup key?

Looks like we should be installing the service_identity module as part of Homer to prevent the first warning. I think we should also be handling the connection refused log inside...