EOF on send

[gustavocovas]

As we suggested on #961, add a verification for io.EOF on the generated code template, along with an integration test

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[gustavocovas]

I signed it!

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

[johanbrandhorst]

This looks great! Just a small question

[johanbrandhorst]

Looks like you need to regenerate the files too, see the contribution guidelines document.

[johanbrandhorst]

The CLA issue can be manually fixed if we can get approval from @jonasarilho your co-author to merge this. A comment in this PR suffices.

[codecov-io]

Codecov Report

Merging #962 into master will decrease coverage by 0.03%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #962      +/-   ##
==========================================
- Coverage   53.26%   53.22%   -0.04%     
==========================================
  Files          40       40              
  Lines        4001     4004       +3     
==========================================
  Hits         2131     2131              
- Misses       1672     1675       +3     
  Partials      198      198

Impacted Files	Coverage Δ
protoc-gen-grpc-gateway/gengateway/template.go	67.03% <ø> (ø)	⬆️
examples/server/a_bit_of_everything.go	0% <0%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0d29f14...c0f90ab. Read the comment docs.

[jonasarilho]

I approve these changes.

[johanbrandhorst]

@achew22 @ivucica could one of you manually approve the CLA please.

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

[johanbrandhorst]

Thanks a lot for the contribution!