in this ticket: https://pagure.io/fedora-infrastructure/issue/6094
we have been requested to add a fcaic alias.
+1s? should be a pretty minor change.
diff --git a/roles/fas_client/files/aliases.template
index d972e57..b00bec5 100644
@@ -343,5 +343,9 @@ blockerbugs: tflink+blockerbugs(a)redhat.com
+# Fedora Community Action and Impact Coordinator
#### The rest of this file is automatically generated - edit using the
While I was debugging settings not saving for Mailman, I found out
that this was caused
by the schema of the "template" table being incorrect.
It had the following gem:
password | timestamp without time zone
I've just ran the following query to make it be identical to what's in the code:
alter table template alter password type character varying;
Can I get +1s on this change?
p.s.: This is about 5 hours old, but seems I sent it to devnull.
With all the work Patrick and Pingou have been doing on pagure lately, it's much faster and it doesn't have lockups as often. Unfortunately it does still have them.
Currently when it does stop processing it's got 4 threads at 100% cpu doing tasks on large git repos. I'd like to bump that to have it start 6 of them and see if this makes the lockups happen less (ie, if the problem is that it locks up if 4 large processes happen to hit at the same time, it should lock up less if theres 6 processes running)
diff --git a/roles/pagure/frontend/templates/0_pagure.conf b/roles/pagure/frontend/templates/0_pagure.conf
index 480b1ef..4b76d20 100644
@@ -3,7 +3,7 @@ WSGISocketPrefix run/wsgi
-WSGIDaemonProcess pagure user=git group=git maximum-requests=1000 display-name=pagure processes=4 threads=4 inactivity-timeout=300
+WSGIDaemonProcess pagure user=git group=git maximum-requests=1000 display-name=pagure processes=6 threads=6 inactivity-timeout=300
WSGIDaemonProcess paguredocs user=git group=git maximum-requests=1000 display-name=paguredocs processes=4 threads=4 inactivity-timeout=300
## Redirects http -> https
The infrastructure team will be having it's weekly meeting tomorrow,
2017-06-01 at 18:00 UTC in #fedora-meeting on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
fedora-infrastructure-meeting-next is the document.
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
> This shared document is for the next fedora infrastructure meeting.
> = Introduction =
> We will use it over the week before the meeting to gather status and info and
> discussion items and so forth, then use it in the irc meeting to transfer
> information to the meetbot logs.
> = Meeting start stuff =
> #startmeeting Infrastructure (2017-06-01)
> #meetingname infrastructure
> #topic aloha
> #chair smooge relrod nirik abadger1999 dgilmore threebean pingou puiterwijk pbrobinson
> = Let new people say hello =
> #topic New folks introductions
> = Status / information / Trivia / Announcements =
> (We put things here we want others on the team to know, but don't need to discuss)
> (Please use #info <the thing> - your name)
> #topic announcements and information
> #info we are now in f26 Beta freeze - everyone
> #info freeze rules are outlined here: https://docs.pagure.org/infra-docs/sysadmin-guide/sops/fedora-releases.html
> #info Slow storage issues continue, but being investigated - kevin
> #info We increased timeouts on kojipkgs to help work around slowness - kevin
> #info Kevin will be out all next week
> = Things we should discuss =
> We use this section to bring up discussion topics. Things we want to talk about
> as a group and come up with some consensus /suor decision or just brainstorm a
> problem or issue. If there are none of these we skip this section.
> (Use #topic your discussion topic - your username)
> #topic FLOCK! - kevin
> = Apprentice office hours =
> #topic Apprentice Open office hours
> Here we will discuss any apprentice questions, try and match up people looking
> for things to do with things to do, progress, testing anything like that.
> = Learn about some application or gsetup in infrastructure =
> (This section, each week we get 1 person to talk about an application or setup
> that we have. Just going over what it is, how to contribute, ideas for improvement,
> etc. Whoever would like to do this, just add the i/nfo in this section. In the
> event we don't find someone to teach about something, we skip this section
> and just move on to open floor.)
> #topic Learn about:
> = Meeting end stuff =
> #topic Open Floor