Megan Potter

@mete89 What is the behaviour you're seeing? It should be functioning. e.g. if you set maxMessages to 1, it should only deliver one message at a time, pausing the stream...

Unrelated, the original issue topic is closed out by: https://github.com/googleapis/nodejs-pubsub/pull/2024 I'll leave this open for discussing the other thing.

@mcasarrubios Thanks for the input. Right now you can already do the basic "wait for dequeue" using these methods: - subscriber.close() - topic.flush() The extra thing we want to add...

There's an end in sight for this problem. 😹 The tentative intent is something like the following: Option 1: Close the subscriber stream, nack everything not sent to a callback,...

Yeah, I think we're on the same page there. Option 2 is basically "I need my service to exit ASAP", the other is the graceful shutdown path.

Thanks for the issue update. The holding more messages as the streams fail is more or less expected, at least until their maximum timeout. The timeout itself sounds transport-related, so...

I wonder if this has something to do with ack IDs being ack'd more than once. It's a server error being returned, though, so someone else might know more. @maheshgattani...

Yeah, I talked with the team and they said this should really be a support request, because otherwise we can't look into the logs and see what's going on with...

This is potentially part of the Node 18+ work (or depends on it).

@lushu Yeah, that makes sense, and I was actually just looking at that code for another question. :) The intention is that those methods are "fire and forget". If exactly...