Deepanshu Agarwal
Deepanshu Agarwal
> ### Batch Subscribe: > Till now, this is how normal subscribe operation works in Dapr: > > > > Well, Ideally this is how Batch Subscribe should flow like:...
For bulk subscribe, for gRPC side, we need a new API for Apps in proto definitions. If we introduce a new API in existing ` service AppCallback `, then it...
> > For bulk subscribe, for gRPC side, we need a new API for Apps in proto definitions. If we introduce a new API in existing `service AppCallback`, then it...
What is the way out for this one then? Can we name new service in such a way that any new Alpha RPCs can be added to it, something like...
Thanks @alecor191 for raising this issue. This is really interesting to see, getting our APIs limits' checked. May be we need to start having more load tests checking APIs limits...
E2E test is failing here, since we are using Dapr 1.8.0, the latest released major version (https://github.com/dapr/js-sdk/blob/c3f6347f632a508944f7b8296298f665f32a9d6f/.github/workflows/test-e2e.yml#L39) But, it needs change from https://github.com/dapr/dapr/pull/5049, specifically https://github.com/dapr/dapr/blob/490ef74dbd06e13a4557a249afd58d1abecb01af/pkg/grpc/api.go#L547
Commented out E2E test for now - E2E tests should pass now. Would un-comment after dapr 1.9 release.