-
-
Notifications
You must be signed in to change notification settings - Fork 17.5k
victorialogs: 1.24.0 -> 1.25.0 #423260
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
Merged
Merged
victorialogs: 1.24.0 -> 1.25.0 #423260
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 hidden or 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.
The upstream uses the new repo here: https://github.com/VictoriaMetrics/VictoriaLogs/blob/8f74a61d479d875a6c13398798183dc922df89b3/Makefile#L14
Uh oh!
There was an error while loading. Please reload this page.
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.
Please see the linked issue in my previous comment (#423260 (comment)), and this PR. VictoriaMetrics/VictoriaLogs#419 and
VictoriaMetrics/VictoriaLogs@7db3660
On the force push, that I did in the morning you see that that was explicitly the value before (which is grabbed from the linked Makefile), but that was not correct, thus resulting in VL not being able to report it's version.
I don't see that we should merge a version with a broken version report, even tho it's wrongly published on 1.25.0 by upstream.
Tho if you strongly ask for that I can ofc force push again the ref with the broken version report
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.
Imo we should leave it working with the "wrong" repo url and change it in the next release
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.
I don't. If it's reported wrong, a fix/workaround is fine
Uh oh!
There was an error while loading. Please reload this page.
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.
The repo url is not wrong according upstream.
If I understand the upstream issue correct all software from Victoria Metrics (organization) is importing the buildInfo from the victoriametrics repo, thus needing the VM repo as into in -X argument.
changing it results in not working versions n info.
As upstream did change the -X argument and not add a new buildInfo that seems to be at least intended rn.
I might be still wrong in what I understand from the written text in the issue/or, but it's at least how .
But let's see if/when upstream changes that.