Various problems seem to be happening in regards to grpc-js

[feywind]

Over the course of the last few months, I've been tracking a number of issues where the answer was "roll back to an earlier version", and often when I ask people to try the newest version, but sub in the gRPC C++ bindings, it also works fine. (Or sometimes even better than the older version.)

There is something going on there that needs to be figured out. I'm making this to track related things independently of adjacent issues.

Potentially related:
#679 (comment)
#788
#789
#818
#825
#850

[Ezard]

@feywind I think #770 is another one

[feywind]

After reading that issue, I think this may also fall into the bucket: #866

[feywind]

Potentially related. #885

[yagodorea]

I saw some bugs were resolved by the latest pubsub release. Is this gRPC issue one of them? If changing the default binding can solve it, can't we make it the default binding in the lib?

[ThomWright]

Could I add grpc/grpc-node#767 as another example of things going wrong because of grpc-js?

Thanks for looking into this, we've been stuck on an old version (0.28.1) for almost a year. It's a case of choosing which bugs are least problematic (we're suffering from #574), and at the moment I'm still convinced that upgrading to v1 is too risky.

[ctavan]

@ThomWright I can feel you 😉 Maybe to bolster you up a bit:

@google-cloud/[email protected]
@grpc/[email protected]

is the first combination in months that really seems to work flawlessly for me, see #850 (comment).

[feywind]

The sort of gestalt I'm seeing lately is that grpc-js is really a lot more stable for everyone, so I'm going to go ahead and close this out. Please feel free to add more comments with examples of problems, though. These examples are being fed into internal notes about pain points everyone has been experiencing.

I'm hoping to get us onto grpc-js 1.x soon, as it's no longer marked as a pre-release.