Spencer Judge
Spencer Judge
Another API that could make sense would be something like: ```rust let mock = setup(); let expectations = mock.take_expectations(); let updated_expectations = expectations.filter(|e| e.call_func == MyMockTypeCall::Foo); mock.set_expectations(updated_expectations) ``` Here `take_expectations`...
Exposing it for users is reasonable but I do think it's worth verifying that everything we need to do can't be done solely in Core. I see no reason it...
@andrepastore Hmm, weird. This definitely isn't some fundamental bug as this code./tonic version is running now in our other SDKs and in our tests etc just fine. Are you using...
Hey @Irvenae - thanks for opening. If you have code that even sometimes repros this, that would be useful. Also, please try out the newest TS SDK, it has an...
@djc I'm happy to accept pulls for removing mockall (can definitely be done, not necessarily easy) and otel (probably pretty easy to make optional). The separate hasher crate is used...
> > mockall (can definitely be done, not necessarily easy) > > Can you briefly explain what the goal/use case of the `MockManualWorkerClient` is? For testing of course. But, in...
It's not the right place to call the cancel, no, the real issue in this case is that the `poller_stream` in that function you are referring to never terminates in...
Looking into this today
@c-thiel That is the way to go - feel free to open a PR. Thanks.
@Elvecent Indeed, they're not implemented in the Rust SDK itself. The Rust SDK in this repo exists only for internal testing purposes at this point and comes with no API...