-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
chore(log_to_metric transform): add missing Cargo feature #18308
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This module is actually used in a few places other than
log_to_metric
so I removed this flagging in #18322There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @jszwedko thanks for the heads-up.
That one was tricky indeed. Can you tell me which component required that parser code?
I did my best to try to find it and couldn't. Also, how come the CI didn't fail for this PR if that was the case?
I had to add that flag to the parser because when compiling Vector with minimal features, I started to get parser import unused errors. I think the correct thing to do is to restore that flag and add the other features that also use it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aha, yeah, I see, we will get dead code warnings. I think it may be safer to just revert this temporarily then and let you reintroduce it with the additional flag handling. Let me do that. You can see the flags that failed to compile in isolation here: https://github.com/vectordotdev/vector/actions/runs/5908210923/job/16027341665 (e.g.
sources-kubernetes_logs
). As you noted, you can see these locally viamake check-component-features
. Just a warning that this check takes a long time 😓 since it tries to compile each feature individually. We can also trigger CI to run it on a new PR from you if that helps.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the heads-up that it's an expensive operation.
I will check out the job output to determine the dependencies and prepare a new PR shortly.
I think it would be a good idea to trigger a CI run for that PR to verify. The second time is the charm!