Various issues related to our use of `tracing`
There were a number of issues found in Brussels related to our use of tracing
. These were, as far as I and @ahf can recall:
- issues with just figuring out how to get anything displayed on the screen in the first instance (the tracing docs don't highlight obvious crates to use, and then figuring out how to pass in a more granular log level than "all @ trace level" took some time)
- issues with interop with crates just using
log
(see also #753) - issues with getting a tracing subscriber (appender? whatever it's called) to log to a file (specifically tla had an issue getting this to work on macOS, and nobody had any idea why)
- we ended up using some hack with passing a callback function from Swift to Rust, and that ended up working; maybe it'd be nice to have an arbitrary "pass a function for logging" thing?
It might be possible to nip a lot of these in the bud by just not using tracing
any more, given we don't seem to be getting any benefit from it, but this is something we should discuss.