Megan Potter

I think the `external` tag isn't the right thing here, but since there's a fix happening elsewhere potentially, I'm going to put it on there. I'll keep an eye on...

Ah, darn. I was hoping 1.0.5 would fix it. I'm going to go ahead and bump the dependency version anyway, in case it helps the others' issues.

Quick update on this, the consensus was that we probably shouldn't actually do the explicit dependency on grpc-js in here, because it might fall out of sync with other libraries...

@shufengh It looks like 2.5.0 is the one that pulled in the new gax version explicitly. Maybe give that one a try? https://github.com/googleapis/nodejs-pubsub/pull/1085

Going through all the existing issues today... is there anyone who's still having this issue on the latest version of the library?

Not that I'm aware, but there is a new grpc-js coming out soon that has more debug info that might help us figure it out. There are some related issues...

The new grpc-js update should be available now, though you might have to remove package-lock.json and `npm install` again to get it. https://github.com/grpc/grpc-node/pull/1658 As before, please set these environment variables...

@arbourd (or anyone else), any luck grabbing some more debug logs for the issue?

@andryichenko Sorry for the late reply on this, but could it be that the publisher piece you showed above is queueing the messages for batch send? You might try decreasing...

I'm not as knowledgable about what happens after it leaves the Pub/Sub library, so it's possible something down in gax/gRPC is doing its own buffering. I can ask the maintainers...