Upgrade tracing-subscriber

[jplatte]

I use tracing-subscriber directly in my project and don't like duplicate dependencies.

[ngugcx]

Is there any special reason why Druid depends on tracing?

[jplatte]

It's a convenience thing, AppLauncher::log_to_console which uses tracing-subscriber on native targets and tracing-subscriber + tracing-wasm on wasm.

I wouldn't personally mind if it was instead removed though 🤷🏼

[sjoshid]

Im assuming the problem here is that you are using version 0.3.2 in your project while druid uses version 0.2.15. So the PR makes druid use version 0.3.2. Now both use version 0.3.2 and problem solved.
But wouldnt you run into same issue if druid uses version > 0.3.2 in future?

[jplatte]

There's not really a big problem here, it's just that build times get longer when you have duplicates of the same crate in the dependency tree. Yes of course druid should upgrade tracing-subscriber again in the future (when there's a breaking change release).

[sjoshid]

The point that I was trying to make was Druid is not going to update to latest and greatest version to satisfy a downstream client.
I empathize with your dependency issues but the real fix would be to completely remove it from Druid.

[jneem]

We can certainly discuss removing the dependency, but at least since it's there for now, we may as well keep it up to date. (Also, annoying that test-env-log broke the build with a semver-compatible update, but 🤷)

[jplatte]

(Also, annoying that test-env-log broke the build with a semver-compatible update, but 🤷)

It only broke CI due to -D warnings.