Heitor Lessa

reopening as @leandrodamascena had to revert yesterday release as this caused a regression for other customers that our test suite did not cover - we're gonna need time to talk...

cc @dreamorosi @hjgraca @jeromevdl so it's on everyone's radar for a good UX and think a name+logic that works for everyone

giving you an answer until tomorrow as to why; we've been heads down on putting controls to prevent future regressions due to optional dependencies we had in the last release,...

hey @CaptainDriftwood appreciate your patience while we resolved a higher priority - created a complete workaround for you at the bottom. I've added `help wanted` and `need-customer-feedback` to help attract...

Idea... **maybe** we could think of using `JMESPath` like we use in multiple places here. We started simple because we knew customers could pluck those values before calling `.evaluate`. JMESPath...

hey @esthermcmahon, thank you so much for taking the time to open this feature request. Are you using DynamoDB or Redis as a persistence storage for Idempotency? The reason we...

(haven't forgotten, adjusting to jet lag from ANZ as I'm back today) - this is a great idea and we were waiting from customer demand to consider it. I'll share...

> unless an exception is encountered This is tricky part. As of now, I can think of these scenarios: * **Handled exceptions**. Code is within a `try/except` block and customers...

> I expect the logger.exception to flush out the buffer like a stack trace > Explicit and backward compatible Yeah, that's the direction we'd go given our tenets. On Monday...

@sthulb when you can, would you mind dropping the memory test you did for verbose log records if kept in a circular buffer for this feature? We're handling some critical...