Ilya Ozherelyev

+1 on David's point. Might be better to introduce a dry run mode and control it with dynamic config.

My reasoning: In my project we use this package and it works great, but goimport keeps pushing lytics/logrus to imports, because it is first on the list, and it really...

Not sure if you've tried/looked, but I've recently found https://github.com/mennanov/limiters. It supports multiple storage engines and has different implementations already. That comes with some limitations of external db requirements, but...

Hey. Could you elaborate what is your usecase? I'm not sure I understand. 1. Cadence provide a way to schedule workflow executions and is meant to tolerate a single server...

hmm in the monorepo the version is set to 0.17.0 and it client works. Let me try 0.17.0 then, might be it will be fine.

Lets release client first, then add a release version of clients that support this feature.

hmm. Could you elaborate? The biggest issue between time and context packages is that context package always use realtime, which defeats any controlled testing environment effort: https://cs.opensource.google/go/go/+/refs/tags/go1.23.0:src/context/context.go;l=689 So, implementing context.Context...

Ok. I'm still not 100% sure if I understood you correctly, but I've updated the PR with the #2 approach. The most considerable flow of this design changes the behavior...

Script for submodules release: https://github.com/cadence-workflow/cadence/pull/6954

This sounds interesting. We are looking into possibilities on onboarding to [fx](https://github.com/uber-go/fx), which simplifies our internal setup and provides the potential to build plugins. However, it is not a high...