Steven L

tbh my first thought is to make `*Logger.With` clone that does not immediately wrap the cores, but just defers it. And then in that deferred structure, actually-wrap and cache the...

How exactly do we treat activities that are started-and-running at the point we reset to? They have the same lifecycle: schedule, then start, then complete, they can fail, and you...

Retries make "started" ambiguous for activities, as it can happen multiple times, so it's a convenient thing that there is no "activity run ID" / activity-start future exposed. But say...

> > The run id does not need to change, because it can't, and there's no desire to change it: it failed > > @Groxx I know why you thought...

Made a quick-n-dirty test with: ```go go func() { for {

Given kakfa in the example: is this intended as like a back-pressure system? So you maintain like 10 workflows processing a kafka stream, and never go over 10, and that...

I don't think builder images are relevant here - they're used to compile some binaries (which do not have ncurses statically linked into them AFAIK), and are then _entirely discarded_....

gonna just close this one - it's still reasonable, but it's also not hard to rebuild.

Merging, will try to follow up this week with a cleanup (if feasible, given the custom behavior I remember... I suspect it won't be, but worth checking on anyway).

Seems like this could be handled with a command-line flag without too much trouble? like: ```go import "flag" wrap := flag.Bool("wrap", false, "if true, launch with panicwrap") flag.Parse() if *wrap...