Status Update
No update yet.
Comments
mb...@appomni.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
pu...@google.com
pu...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
If you are looking for a faster resolution and dedicated support for your issue, I kindly request you to file a support ticket by clicking
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
Description
Problem you have encountered: While writing a unit test for subscribing, I noticed that my concurrency limits were not working. When debugging, the max outstanding messages request in a streaming pull request is not being honored when using the Pub/Sub emulator. I push 5 messages, send a streaming pull request with
max_oustanding_messages=2, and the streaming pull response object has all 5 messages.I do not see any limitation on flow control listed here:https://cloud.google.com/pubsub/docs/emulator#known_limitations
What you expected to happen: The max outstanding messages should be honored.
Steps to reproduce:
Publish 5 messages to a topic.
Send an initial request using an async generator (python):
The resulting
responseobject (StreamingPullResponse) has all 5 message inresponse.received_messages(RepeatedComposite).Other information (workarounds you have tried, documentation consulted, etc):