#10361 Fatal Error (500) accessing a PR
Closed: Fixed with Explanation by mikelo2. Opened by mikelo2.

I've created a PR for a project and when I try to access I get an error 500.

https://src.fedoraproject.org/rpms/duplicity/pull-request/2


@pingou Can you help here?

Metadata Update from @mohanboddu:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: medium-gain, medium-trouble, ops

The error is:

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/pagure/ui/filters.py", line 846, in get_patch_stats
    output = pagure.lib.git.get_stats_patch(patch)
  File "/usr/lib/python3.6/site-packages/pagure/lib/git.py", line 2997, in get_stats_patch
    "Unable to properly retrieve the stats for this patch"
pagure.exceptions.PagureException: Unable to properly retrieve the stats for this patch

So there is something odd about the PR. If we know which fork/repo it came from,
it may be worth checking the commits diff there.

My fork and branch is: https://src.fedoraproject.org/fork/mikelo2/rpms/duplicity/tree/misc-changes

https://src.fedoraproject.org/fork/mikelo2/rpms/duplicity/c/3b6bbc52c97af4a2d6853127fa1dd99681872acd is the only commit in that branch, and it seems to load/diff ok...

Apart from the 3 modified files, there was another entry:

+ Subproject commit dbcd107e94afc5f2e6dde47a1de1e9a1d5fdc09b

pr-issue.png

i cloned the upstream repo inside the project and somehow it got committed for the PR.

Once I've removed I'm able to see the PR.

Thanks for your help @kevin, @mohanboddu & @pingou

Metadata Update from @mikelo2:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

Metadata