Skip to content

Conversation

@mauri870
Copy link
Member

Proposed commit message

The bitSize argument in strconv.ParseFloat should be either 32 or 64.
Any value other than 32 will default to 64 in the current implementation,
though this behavior is undocumented, making it undefined.

See https://cs.opensource.google/go/go/+/refs/tags/go1.23.0:src/strconv/atof.go;l=704-708.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

The bitSize argument in strconv.ParseFloat should be either 32 or 64.
Any value other than 32 will default to 64 in the current implementation,
though this behavior is undocumented, making it undefined.

See https://cs.opensource.google/go/go/+/refs/tags/go1.23.0:src/strconv/atof.go;l=704-708.
@mauri870 mauri870 added cleanup Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team labels Sep 11, 2024
@mauri870 mauri870 requested a review from a team as a code owner September 11, 2024 12:57
@mauri870 mauri870 requested review from faec and leehinman September 11, 2024 12:57
@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Sep 11, 2024
@mergify
Copy link
Contributor

mergify bot commented Sep 11, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @mauri870? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit

@mergify
Copy link
Contributor

mergify bot commented Sep 11, 2024

backport-8.x has been added to help with the transition to the new branch 8.x.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Sep 11, 2024
@mauri870 mauri870 mentioned this pull request Sep 11, 2024
6 tasks
@mauri870 mauri870 merged commit 6e93c27 into elastic:main Sep 11, 2024
mergify bot pushed a commit that referenced this pull request Sep 11, 2024
The bitSize argument in strconv.ParseFloat should be either 32 or 64.
Any value other than 32 will default to 64 in the current implementation,
though this behavior is undocumented, making it undefined.

See https://cs.opensource.google/go/go/+/refs/tags/go1.23.0:src/strconv/atof.go;l=704-708.

(cherry picked from commit 6e93c27)
@mauri870 mauri870 added backport-skip Skip notification from the automated backport with mergify and removed backport-8.x Automated backport to the 8.x branch with mergify labels Sep 12, 2024
pierrehilbert pushed a commit that referenced this pull request Sep 17, 2024
The bitSize argument in strconv.ParseFloat should be either 32 or 64.
Any value other than 32 will default to 64 in the current implementation,
though this behavior is undocumented, making it undefined.

See https://cs.opensource.google/go/go/+/refs/tags/go1.23.0:src/strconv/atof.go;l=704-708.

(cherry picked from commit 6e93c27)

Co-authored-by: Mauri de Souza Meneguzzo <[email protected]>
@khushijain21 khushijain21 mentioned this pull request Jun 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-skip Skip notification from the automated backport with mergify cleanup Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants