Megan Potter

@mnahkies Sorry this has languished a bit. gRPC related issues are hard to diagnose cleanly, and we have a few outstanding ones. There is some new debug info going into...

After taking a look at all of this, and talking to some others, I am coming around to thinking that this might be better solved by server side publisher flow...

I think I misunderstood the publisher flow control plans, so we will probably still need the submitted patch.

What Kamal said. ^ I think that several issues are going to be closed by getting publisher-side flow control in place. It's not there yet in Node, though.

Taking a look at some old issues in here, a few comments: - @mgabeler-lee-6rs To be completely honest, there has been a lot of discussion about who owns the emulators...

@WesCossick I thought I'd commented here, sorry - at the moment we don't have a tag for the docs for a subscription retry policy sample, but I'm okay leaving this...

@anguillanneuf pointed me at this: https://cloud.google.com/pubsub/docs/admin#pubsub_update_push_configuration-nodejs which is also this: https://github.com/googleapis/nodejs-pubsub/blob/main/samples/modifyPushConfig.js You should be able to do a similar thing by calling `setMetadata` with your retry policy instead of `modifyPushConfig`....

@QuestionAndAnswer Thanks for the super detailed report. I'll have to go over this in more detail, but I'll mark it as a bug for now. I like your editor's comment...

Quick (sadly content-less) update - no changes here yet, but I've been on a bit of a feature development rotation and hope to get back to these issues.

I stared at this for a while today, and I'm not as familiar with this bit of the library, but I don't know why we'd want to dispense messages from...