tracing-distributed@0.4.0, tracing-honeycomb@0.4.3 - tracing-subscriber 0.3 compatibility + Error impls

[jfhbrook-at-work]

This PR takes #12 and #13 and packages them up into a release branch:

• Updates tracing-subscriber to v3 in tracing-distributed (Update dependencies to tracing-subscriber 0.3 #12)
• Updates arguments passed to trace::Event in tracing-distributed (Update dependencies to tracing-subscriber 0.3 #12, impl Error for TraceCtxError and ParseSpanIdError #13)
• Updates tracing-honeycomb to accept tracing-distributed v0.3 or v0.4 (both are compatible)
• Implements Error trait for TraceCtxError and ParseSpanIdError (impl Error for TraceCtxError and ParseSpanIdError #13)
• Implements Display trait for TraceCtxError
• Bumps tracing-subscriber to v0.4.0 (breaking)
• Bumps tracing-honeycomb to v0.4.3 (additive)

A general release plan taking preroll and our apps into account is in the comments.

[jfhbrook-at-work]

My biggest question is how to test this - we would need to update the versions in https://github.com/eaze/preroll and then update preroll in one (some?) of our apps.

One way we can do this is to release tracing-distrubuted and preroll with versions 0.4.0-beta.0 and 0.10.0-beta.0 respectively, make an app use those versions, and then go GA when that deploys without major incident.

Does this sound reasonable @ericsampson ?

cc @Infrasonics

[jfhbrook-at-work]

My plan:

• Release tracing-distributed@0.4.0 (breaking)
• Release tracing-honeycomb@0.4.3 (additive)
• PR + release preroll@0.10.0-beta.0 (breaking, beta)
• Deploy preroll@0.10.0-beta.0 to an internal service, iterate until the service is happy
• PR + release preroll@0.10.0

As far as I know this PR is ready to go and I feel pretty comfortable with the plan. But I'll sleep on it beforehand, in case either me or someone else has a shower thought.

[ceejbot]

🐑 it!

[ericsampson]

What you said makes sense to me for the rationale to specify that both 0.3 and 0.4 of tracing-subscriber are compatible, but I wouldn't mind getting ceej or Chris to double check since I'm not a cargo dep expert yet 😅

Thanks for doing this Josh! We should probably cc the original reporter once the packages are published.

Do you know how to publish the packages?

[jfhbrook-at-work]

I don't know how yet, but I'm sure it's a command in cargo and I'm confident that as an owner I'll have the appropriate permissions. I'll try it out today and we'll see!

[Infrasonics]

For checking what gets zipped, have a look at cargo package.
When ready cargo publish does the job. Needs a token for the used registry (e.g. crates.io).

[jfhbrook-at-work]

Published tracing-distributed@0.4.0 and tracing-honeycomb@0.4.3. Cheers!