Claire Foster

> I cannot decide if it is too much of a magic to happen automatically, though. Haha, I suspect it probably is :-) If log record serialization is done via...

I don't think there's a one-size-fits-all approach. I suspect that for `Distributed` it would be fairly natural to use `serialize` because `Distributed` seems to target cases where all processes are...

Sure, sounds good to vendor that fix behind a `VERSION` check.

This is a little confusing, given that I think you vendored most of ProgressLogging in julia-vscode over at https://github.com/julia-vscode/julia-vscode/pull/1579? Overall if these kind of hacks are really required, it seems...

This looks reasonable to me if it solves the `DiffEqBase` issue. As I said over at `DiffEqBase`, I feel like it's something we should replace in the longer term by...

Good suggestion, I think something like that is the right way to go.

> but this is not possible anymore with `Progress` and currently there exists no visualization backend for `ProgressLogging` that would print this additional information. Actually `@logprogress` can still accept key...

With the current version of the code you can certainly use a separate sticky message if you like. I think it's a bit of a hack though if you intend...

Oh by the way, I should point out that with the `@logprogress` example above I've changed the progress bar `name` every iteration which will allow you to manually insert whatever...

Hmm, it seems weirdly backward to have the normal log message become the name of the progress bar and then to add a separate `message` key which is also the...