Bug: fix slice init length
Proposed commit message
fix slice init length
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.asciidocorCHANGELOG-developer.next.asciidoc.
Disruptive User Impact
Author's Checklist
- [ ]
How to test this PR locally
Related issues
Use cases
Screenshots
Logs
💚 CLA has been signed
This pull request does not have a backport label. If this is a bug or security fix, could you label this PR @dufucun? 🙏. 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-v8./d.0is the label to automatically backport to the8./dbranch./dis the digit
❌ Author of the following commits did not sign a Contributor Agreement: 14cb6ed
Please, read and sign the above mentioned agreement if you want to contribute to this project
signed
Thanks!
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)
Thanks for your review!
/test
run docs-build
backport-8.x has been added to help with the transition to the new branch 8.x.
@dufucun, it looks like the linter is complaining about this:
Error: libbeat/processors/ratelimit/limit.go:49:41: SA1030: 'bitSize' argument is invalid, must be either 32 or 64 (staticcheck)
v, err := strconv.ParseFloat(valueStr, 8)
^
Error: issues found
Ran golangci-lint in 429865ms
@ycombinator The linter error should be fixed once https://github.com/elastic/beats/pull/40753 is merged.
Edit: I just merged the PR and rebased this branch.
buildkite test this
buildkite test this
/test
run docs-build
/test
run docs-build
/test
run docs-build
Would be good to get this merged. The changes are very simple and logically correct. The CI errors in the previous builds appear to be unrelated with the changes.
/test
run docs-build
Thanks
/test
/test
run docs-build
run docs-build