Hitting a null object error sporadically

[JoeSzymanskiFAN]

Hitting a null object error sporadically

[sorenlouv]

Can you check if the logs contain the stack trace for the error Cannot read properties of null (reading 'remoteConfigHistory')?

Logs are located in ~/.backport/

[JoeSzymanskiFAN]

I see the following at the end of the logs

{"level":"error","message":"Unhandled exception: Cannot read properties of null (reading 'remoteConfigHistory')","metadata":{"stack":"TypeError: Cannot read properties of null (reading 'remoteConfigHistory')
    at getSourceCommitBranchLabelMapping (/opt/homebrew/lib/node_modules/backport/dist/lib/sourceCommit/parseSourceCommit.js:144:56)
    at parseSourceCommit (/opt/homebrew/lib/node_modules/backport/dist/lib/sourceCommit/parseSourceCommit.js:21:44)
    at fetchCommitBySha (/opt/homebrew/lib/node_modules/backport/dist/lib/github/v4/fetchCommits/fetchCommitBySha.js:46:54)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async fetchCommitsByPullNumber (/opt/homebrew/lib/node_modules/backport/dist/lib/github/v4/fetchCommits/fetchCommitByPullNumber.js:89:20)
    at async Promise.all (index 0)
    at async getCommits (/opt/homebrew/lib/node_modules/backport/dist/lib/getCommits.js:41:35)
    at async backportRun (/opt/homebrew/lib/node_modules/backport/dist/backportRun.js:61:19)"},"timestamp":"2024-04-03 15:36:07"}

[sorenlouv]

Thanks. The problem is happening here so it looks like there is no mergeCommit. Has the PR in question been merged?

backport/src/lib/sourceCommit/parseSourceCommit.ts

Line 281 in 24dc0f8

sourcePullRequest?.mergeCommit.remoteConfigHistory.edges?.[0]?.remoteConfig;

[JoeSzymanskiFAN]

Yes, it has been merged via a squash into the source branch in question.

[JoeSzymanskiFAN]

Just want to confirm that I pulled the latest version directly and was able to finish a dry run against the PRs that previously were failing. I think I'll need this to be released at some point officially.

[sorenlouv]

Thanks for testing it, much appreciated! I've released the fix in v9.4.6