Go vet complains on composite literal uses unkeyed fields #5690
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
``` Checking file template/config.go Checking file template/load.go Checking file template/processor.go Checking file template/template.go Checking file template/processor_test.go template/processor_test.go:141: github.com/elastic/beats/libbeat/common.DynamicType composite literal uses unkeyed fields template/processor_test.go:147: github.com/elastic/beats/libbeat/common.DynamicType composite literal uses unkeyed fields template/processor_test.go:153: github.com/elastic/beats/libbeat/common.DynamicType composite literal uses unkeyed fields Checking file template/template_test.go exit status 1 ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was found with #5687, this problems does not seems to be triggered on the CI, only on my local environment when I run
make check, I am runninggo 1.9.2, I will do a bit more check on the CI to see why this is not triggered.