stream.stop does not work immediately after subscribe in dapr
Open
area/pubsub
bug
- Dominant language
- JavaScript
- Stars
- 217
- Forks
- 104
- PR merge metrics
- No merged PRs in 30d
Description
After subscribe, a gRPC connection is created, but the streamId is only initialized after the Emitter event is triggered. This process takes some time. Calling stream.stop before the streamId is ready causes it to return silently without stopping or throwing an error.
Relevant code: src/implementation/Client/GRPCClient/configuration.ts:118
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.