proto/profile.proto: fix typo

[srenatus]

No description provided.

[codecov-io]

Codecov Report

Merging #577 (de610f2) into master (3dbeb62) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #577      +/-   ##
==========================================
- Coverage   66.97%   66.96%   -0.02%     
==========================================
  Files          78       78              
  Lines       14160    14160              
==========================================
- Hits         9484     9482       -2     
- Misses       3842     3843       +1     
- Partials      834      835       +1     

Impacted Files	Coverage Δ
.../github.com/google/pprof/internal/report/source.go	80.76% <0.00%> (-0.65%)	⬇️

---

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 3dbeb62...de610f2. Read the comment docs.

[kalyanac]

Please make it "element-wise"

[srenatus]

Sure!

[srenatus]

✔️ changed

[srenatus]

Ping! It's not like the world would stop without this fixed, but can we just merge it? 😃

[srenatus]

Thanks 🍰

[aalexand]

Thanks 🍰

I actually haven't merged, I only rebased :) Some tests are failing for some reason.

[srenatus]

@aalexand yeah but you've reacted 😉 thanks for that.

[google-cla]

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 with @googlebot 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.

[aalexand]

@srenatus CLA check fails now for some reason. Do you have the CLA signed?

[srenatus]

@aalexand I've switched jobs and thus changed my primary email on github. I'll follow up on this issue! Sorry for delaying this.

[srenatus]

@aalexand Is there anything I can do to re-trigger a CLA check? I think it should be sorted now.

[google-cla]

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 with @googlebot 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.

[kalyanac]

Restarted checks after #580 is merged.

[kalyanac]

@srenatus Please follow the instructions from @google-cla bot in #577 (comment) to sign the CLA.

[google-cla]

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 with @googlebot 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.

[kalyanac]

@srenatus CLA bot is still not able to verify that you signed it. PR cannot be merged until it is signed.

[srenatus]

@kalyanac thanks, I'll try to take care of this.

[google-cla]

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 with @googlebot 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.

[kalyanac]

@srenatus CLA bot is still not able to verify that you signed it. PR cannot be merged until it is signed.

[srenatus]

@kalyanac yeah it's on us. We're looking into it. Please bear with me 😄

[srenatus]

@googlebot I signed it!

[srenatus]

Fiiinaaaalllly 🎉