Steven L

yeah, that's an inconsistency we should address 🤔 that said, tbh I'd much prefer to get rid of all multi-value APIs like this. they're significantly harder to make changes to,...

As @Gurpartap points out, this has always been possible, and quite simply. Or people can write a downright trivial loop over instance methods -> call `activity.Register` to do it implicitly...

aah, sorry - I didn't notice the CLA was needed because you're a new contributor. @adilhafeez: if you click the details on that `license/cla` check, we just need that filled...

aaaagh dangit: ``` 2023-04-07T04:03:35.128Z FATAL loggerimpl/logger.go:143 Start workflow with err {"error": "code:unimplemented message:unrecognized procedure \"uber.cadence.api.v1.WorkflowAPI::StartWorkflowExecution\" for service \"cadence-frontend\"", "logging-call-at": "client_integration_test.go:235"} ``` that's probably going to be fatal to this.

well. it requires rewriting both proto and generated code, because yarpc is insufficiently configurable, but it's pretty simple and it does seem to work.

> So the assumption of this algorithm is that the requests may not be evenly distributed among the hosts, but the distribution is somewhat stable and does not fluctuate. Is...

> 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...

Hmm 🤔 I get how this is a problem with our old pinned version internally but... why hasn't it been a problem all along? Seems like this probably changed at...

hmm. seems like something might be messed up in our CI pipeline 🤔

Ah, excellent news: https://github.com/stretchr/testify/issues/608 There is a way to inject testing.T into the mock, which should *absolutely* be done... but it's not yet released :| Bah. Once that's released, this...