Avoid unnecessary 500 panic when a commit doesn't exist (#28719) #28721
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.
Backport #28719 by @wxiaoguang
In #26851, it assumed that
Commit
always exists whenPageIsDiff==true
.But for a 404 page, the
Commit
doesn't exist, so the following code would cause panic because nil value can't be passed as string parameter toIsMultilineCommitMessage(string)
(or the StringUtils.Cut in later PRs)