Megan Potter
Megan Potter
@JaegarSarauer Thanks for the report and all the info. The Node library for Pub/Sub doesn't currently support Exact Once, but it's a feature that's currently in progress.
Well, slight qualification: 2.19.3 has a patch that should keep it from crashing when dealing with EO ack IDs (which are much larger), but there isn't functionality to deal with...
@JaegarSarauer Ah, thanks for the follow-up (sorry for my slow follow-up follow-up). I'm hoping we'll have proper exactly-once support in Node soon but it's good you found a solution.
@shoxsz It is, but it requires a fair amount of client library support to work gracefully and correctly. Specifically, we need to allow users to get a response from calling...
@shoxsz It hasn't been merged, but it's in the later stages of development right now, fingers crossed that it won't be too long.
I'll reopen this.
I'm going to close this issue because the flaky test seems to be a product of an issue talking with the service, and that's got an internal bug now (254095632).
Looks like service issues. @kamalaboulhosn is there anything to look at here service-side? These are also related: https://github.com/googleapis/nodejs-pubsub/issues/1641 https://github.com/googleapis/nodejs-pubsub/issues/1645
I'm going to close this issue because the flaky test seems to be a product of an issue talking with the service, and that's got an internal bug now (254095632).
Using a fresh install and Node 12, I'm unable to repro this locally. I tried both npm 6 and 8, no luck.