Unexpected behavior of SendEach method

[xantinium]

Hi there!
I have encountered a problem with the non-obvious behaviour of the SendEach method. For now, it stops sending the batch and returns an error, if an invalid message presents in batch. So I cannot correctly process the result of the method on my side.

Test case:

1. prepare slice of 500 messages. the one in the middle is invalid (e.g. the token is empty)
2. call method SendEach with that slice

Expected result: method will return BatchResponse with filled counters (like SuccessCount=499 and FailureCount=1)
Actual result: method returning error and skips sending of the rest messages.

Or is this an intentional behavior?

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[lahirumaramba]

Hey @xantinium , we have optimized the sendEach*() functions in #695 and the changes are now available in v4.17.0.
This change should reduce the CPU usage and implement early validation: All messages are now validated upfront. If any message is invalid, the function returns an error immediately without attempting to send any messages. Please create a new issue if you are still experiencing problems. Thanks!