#6083 Fatal Error (500) when create pull request in upstreamfirst.fedorainfracloud.org
Closed: Upstream 2 years ago Opened 2 years ago by zsun.


Metadata Update from @tflink:
- Issue assigned to tflink

2 years ago

I think this has been fixed - I'm able to do PRs against some test repos now (that have been deleted).

Please re-open if you're still seeing the issue

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

2 years ago

Hi Tim,

Please see the screenrecord, it still show 500 error but in later steps now.

upstreamfirst-1.ogv

Metadata Update from @zsun:
- Issue status updated to: Open (was: Closed)

2 years ago

I just checked and saw it did create the PR. But the 500 error is not expected.

I think I've found the root cause of the 500. On the bright side, it doesn't look like the error can affect the PR itself and is mostly an annoyance.

I'll continue to work on getting this fixed - throwing 500s on PR is not ideal behavior, to say the least

I've filed an issue against pagure (https://pagure.io/pagure/issue/2312) and submitted a PR to fix the issue (https://pagure.io/pagure/pull-request/2314).

That change is hotfixed into the upstreamfirst instance and PRs shouldn't be getting 500s anymore.

Great! Lets close this in favor of the upstream bug/pr now.

:space_invader:

Metadata Update from @kevin:
- Issue close_status updated to: Upstream
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Attachments 1
Attached 2 years ago View Comment