Richard Bradfield

> > Hmm, not a huge issue since we don't call `setenv`. We only need chrono for formatting logs, right? > > Agree - @tiny-http doesn't seem to be vulnerable...

Hi, In case it's any use to your team, it looks like the battery issue (in my case anyway, Galaxy S7, Android 7.0) is caused by the ZMessagingService in the...

We'll need to adjust the feature matrix for CI because we can't compile with both the SSL implementations. > Also, based on https://kerkour.com/rust-crate-backdoor I think it would be good practise...

Thanks @3xmblzj5 as ever. I'll cut a release for this this week.

In the two weeks since you opened this, `time-rs` has gone up another minimum supported Rust version.... If you want to change this to bring us up to 1.57 I'll...

We've dropped the low MSRV test case because upstream libraries make no effort to support it, so it's basically impossible for us to to do so without reimplementing half the...

Time has a frustrating MSRV policy summarised as "the last six months", given Rust's release cadence basically means the last 4 point releases. We can consider pinning time but you...

Yeah that's my concern with continually updating it like this. We can probably pin the version without any ill effect if we don't export the type but I'd have to...

Closing as we dropped the mandatory test on old Rust versions and will just deal with issues as they arise.

Excellent news, I'll close the issue and if it pops up again feel free to reopen.