-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[processor/deltatocumulative]: investigate possible int overflows in internal/data/expo
#34828
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
/label processor/deltatocumulative -needs-triage |
Pinging code owners for processor/deltatocumulative: @sh0rez @RichieSams @jpkrohling. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I was not able to reproduce the problem locally with the current state of main branch and with gosec. Are you able to reproduce it with Thanks! |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
processor/deltatocumulative
What happened?
gosec
linter started flagging possible integer overflow errors in recent versions:while these are not necessarily real security implications, we must investigate
Collector version
bddc8c2
The text was updated successfully, but these errors were encountered: