Skip to content

Conversation

lunny
Copy link
Member

@lunny lunny commented Apr 25, 2019

fix #6702

@lunny lunny added this to the 1.9.0 milestone Apr 25, 2019
@lafriks
Copy link
Member

lafriks commented Apr 25, 2019

Drone fail

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Apr 25, 2019
@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Apr 25, 2019
@codecov-io
Copy link

codecov-io commented Apr 25, 2019

Codecov Report

Merging #6754 into master will decrease coverage by 0.02%.
The diff coverage is 7.14%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #6754      +/-   ##
==========================================
- Coverage   41.03%   41.01%   -0.03%     
==========================================
  Files         421      421              
  Lines       57955    57967      +12     
==========================================
- Hits        23781    23773       -8     
- Misses      31017    31035      +18     
- Partials     3157     3159       +2
Impacted Files Coverage Δ
models/error.go 32.08% <0%> (-0.43%) ⬇️
models/pull.go 50.41% <0%> (-0.14%) ⬇️
routers/repo/issue.go 35.58% <20%> (-0.17%) ⬇️
modules/log/event.go 64.46% <0%> (-1.53%) ⬇️
routers/repo/view.go 42.02% <0%> (-1.02%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ec2d489...fa7feea. Read the comment docs.

@lafriks
Copy link
Member

lafriks commented Apr 25, 2019

Where does it check for this new error?

@lunny
Copy link
Member Author

lunny commented Apr 25, 2019

@lafriks GetLastCommitStatus now will check if the headRepo exist or not, and will return new error ErrPullRequestHeadRepoMissing. The panic caused by unchecked headRepo nil.

@lafriks
Copy link
Member

lafriks commented Apr 25, 2019

But shouldn't we check later for that error and show some kind of error in PR?

@lunny
Copy link
Member Author

lunny commented Apr 25, 2019

When list pull requests, the last commit status error could be ignored.

@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Apr 26, 2019
@lunny lunny merged commit 4c34bc1 into go-gitea:master Apr 26, 2019
@lunny lunny deleted the lunny/fix_pull_list branch April 26, 2019 03:03
@lunny
Copy link
Member Author

lunny commented Apr 26, 2019

v1.8 don't have this problem.

@ntimo
Copy link

ntimo commented Apr 30, 2019

Is this going to be backported to 1.8? :)

@lunny
Copy link
Member Author

lunny commented Apr 30, 2019

v1.8 should not be affected by this issue.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Panic when viewing pull requests on a repo with a deleted fork
7 participants