-
Notifications
You must be signed in to change notification settings - Fork 317
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
Release Drafter crashes with "Cannot read property 'login' of null in releases.js" when a pull request submitter is deleted #301
Comments
We also experience issues with draft being created. We merged several PRs in master branch, but the draft wasn't created. |
@rihardssceredins could you please add links to your configurations? The issues might be unrelated |
Our repos ar private so I'm going to post it here. We use the same configuration across all repos. In some repos it works perfect, in some it doesn't or is seriously delayed. I mean after PR is merged the draft may appear between a minute and several hours.
|
After running the Release Drafter using GitHub Actions in one of the affected repos we see that:
Code: https://github.com/toolmantim/release-drafter/blob/v5.2.0/lib/releases.js#L153 , looks like PR author is If so, it might be a regression after #164 in 5.0.0. CC @TimonVS |
After migrating to GitHub Actions releases are drafted correctly when each
PR is merged but I do see the same error message Oleg mentioned.
One other thing I noticed. Release isn’t drafted if no release has
previously been created in the repo. Will paste error in a moment.
On Tue, 17 Sep 2019 at 12:12, Oleg Nenashev ***@***.***> wrote:
After running the Release Drafter using GitHub Actions in one of the
affected repos we see that:
08:55:09.968Z ERROR event: Cannot read property 'login' of null (id=960355aa-000c-40cc-8022-c170ce26de0f)
TypeError: Cannot read property 'login' of null
at acc.push.categorizedPullRequests.(anonymous function).map.pullRequest (/app/lib/releases.js:153:43)
at Array.map (<anonymous>)
at orderedCategories.reduce (/app/lib/releases.js:149:12)
at Array.reduce (<anonymous>)
at generateChangeLog (/app/lib/releases.js:136:6)
at module.exports.generateReleaseInfo (/app/lib/releases.js:179:17)
at app.on (/app/index.js:69:25)
--
event: {
"event": "push",
"id": "960355aa-000c-40cc-8022-c170ce26de0f",
"repository": "jenkinsci/gradle-plugin"
}
Code:
https://github.com/toolmantim/release-drafter/blob/v5.2.0/lib/releases.js#L153
, looks like PR author is null due to whatever reason. Maybe a deleted
GitHub account?
If so, it might be a regression after #164
<#164> in 5.0.0. CC
@TimonVS <https://github.com/TimonVS>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#301>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFQHRNQLIKKVJU3YPBZUWLTQKCNQTANCNFSM4IUGWUZA>
.
--
Sent from Gmail Mobile
|
This is the output from GitHub Actions when an app has no releases and you run release-drafter. I've redacted the repo name in the output.
|
Fix release-drafter#301 - Prevent crash when a pull request author is unknown
I confirm that deleted users were a root cause for us:
@toolmantim @Casz @timja @wolfs ready for review |
Fix has been released in v5.3.1 |
Thanks a lot! |
Hi all! We use the GitHub app to run Release Drafter in the Jenkins project. We use a centralized configuration which runs across 80 repositories ATM. Currently it works for the most of the repositories really well, except the diagnosability issues (I'd guess migration to GitHub Actions or self-hosting would be a right step for our project scale).
Yesterday we hit an issue with https://github.com/jenkinsci/gradle-plugin . The release drafter was enabled there yesterday, and the App was enabled for the repo. Everything looks fine AFAICT, but the changes are not being generated.
It would be great if somebody could take a look at the application logs so that we kno the root cause of the issue
CC @wolfs
The text was updated successfully, but these errors were encountered: