Pull requests generating 500 error #13346
Labels
No labels
announcement
anubis
authentication
aws
backlog
blocked
bodhi
ci
cloud
communishift
copr
database
day-to-day
dc-move
deprecated
dev
discourse
dns
downloads
easyfix
epel
firmitas
forgejo_migration
Gain
High
Gain
Low
Gain
Medium
gitlab
greenwave
hardware
help wanted
high-trouble
koji
koschei
lists
low-trouble
medium-trouble
mirrorlists
monitoring
Needs investigation
odcs
OpenShift
ops
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
release-monitoring
releng
request-for-resources
s390x
security
SMTP
sprint-0
sprint-1
src.fp.o
staging
unfreeze
waiverdb
websites-general
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
infra/tickets#13346
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description of request
I have two packit generated branches that generate 500 errors when I try to create a pull request form them. One is:
https://src.fedoraproject.org/fork/orion/rpms/libmamba/diff/rawhide..rawhide-update
the other is:
https://src.fedoraproject.org/fork/orion/rpms/python-conda-index/diff/rawhide..rawhide-update
There's a traceback that seems related to this:
So ... I technically fixed this by changing the code on disk from:
...to:
...and then restarting httpd/pagure so it reloaded that file.
Upstream is already slightly different, but that bit is the same:
https://pagure.io/pagure/blob/master/f/pagure/ui/filters.py#_150
I'll open a bug upstream, but at least it should work for a bit. Not sure if we want to keep this issue open, or close it now.
Upstream issue: https://pagure.io/pagure/issue/5552
Well, upstream is pretty much dead at this point.
I guess we should add a patch to the epel8 build and deploy it, or setup a hotfix in ansible that applies this if we think it's the right approach.
I did a scratch build of an rpm with the fix: https://koji.fedoraproject.org/koji/taskinfo?taskID=145655907
@abompard I heard you had a couple of patches you wanted to get into a new build ... if you ping me on matrix with them or something, I can add them and do a real build in f44-infra tomorrow.
@james Wouldn't it be better to add patches to ansible directly? There is even task file for that
infra/ansible@0ea1c9f292/roles/distgit/pagure/tasks/patches.ymlA few things to note: pagure01/pagure-stg01 are rhel8 hosts. ;) So we need epel8 builds.
The thought I think was to do actual epel8 builds so we update any people who are still using it on rhel8.
Ah yeah, the patches that we currently deploy are in
/srv/web/infra/bigfiles/hotfixes/pagure/on batcave, could you try to add them too please? That would be great.Did this ever get added there? I don't see it off hand, but might be missing it..