-
Notifications
You must be signed in to change notification settings - Fork 603
Fix scripts/update-contributors.pl CONTRIBUTORS screening #2125
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
Fix scripts/update-contributors.pl CONTRIBUTORS screening #2125
Conversation
Possible unintended interpolation of @users in string
Bareword "true" not allowed
Bareword "false" not allowed
Execution of ... aborted due to compilation errors
Recent commit daa76f4 broke scripts/update-contributors.pl syntax (see
error messages quoted above) and lower-case comparison logic,
effectively disabling CONTRIBUTORS checks.
An `if` statement with a false condition and without an `else` clause always succeeds, setting `$?` to 0 (including cases when the condition command itself fails to execute).
|
I did not have a chance to review #2109. The problem was discovered by @eduard-bagdasaryan while working on an unrelated improvement. I am asking him to review this PR. Some of the problems fixed in this PR can be seen in recent PRs: CI logs show errors despite overall successful source-maintenance checks. |
|
LGTM |
kinkie
left a comment
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 fixing this
Possible unintended interpolation of @users in string
Bareword "true" not allowed
Bareword "false" not allowed
Execution of ... aborted due to compilation errors
Recent commit daa76f4 broke scripts/update-contributors.pl syntax (see
error messages quoted above) and its lower-case comparison logic,
effectively disabling CONTRIBUTORS checks.
Also do not hide update-contributors.pl execution failures. Buggy
failure detection contributed to the above problems ignored by CI tests.
| result=$? | ||
| ./scripts/update-contributors.pl --quiet < authors.tmp > CONTRIBUTORS.new || return | ||
| updateIfChanged CONTRIBUTORS CONTRIBUTORS.new \ | ||
| "A human PR description should match: $vettedCommitPhraseRegex" || return |
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.
Don't we need to delete authors.tmp if updateIfChanged() fails?
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.
Don't we need to delete
authors.tmpifupdateIfChanged()fails?
In the ideal world, probably yes. In that ideal world, such cleanup would be controlled by a configuration option that would allow folks to leave temporary files for failure triage.
In reality, the benefits from removing authors.tmp when git, update-contributors.pl, or updateIfChanged() fails are not worth the effort required to guarantee and control that removal. And the harm is relatively small because these temporary files are not going to accumulate across failures.
…e#2125) Possible unintended interpolation of @users in string Bareword "true" not allowed Bareword "false" not allowed Execution of ... aborted due to compilation errors Recent commit daa76f4 broke scripts/update-contributors.pl syntax (see error messages quoted above) and its lower-case comparison logic, effectively disabling CONTRIBUTORS checks. Also do not hide update-contributors.pl execution failures. Buggy failure detection contributed to the above problems ignored by CI tests.
|
queued for backport to v7 |
Recent commit daa76f4 broke scripts/update-contributors.pl syntax (see
error messages quoted above) and its lower-case comparison logic,
effectively disabling CONTRIBUTORS checks.
Also do not hide update-contributors.pl execution failures. Buggy
failure detection contributed to the above problems ignored by CI tests.