+1
On Thu, 5 Mar 2020 at 01:00, Kevin Fenzi wrote:
> We have been getting complaints from copr users that they are hitting
> out of date cloudfront cached data when they are doing builds.
> We are syncing not all that often currently, and sometimes if a updates
> push or rawhide compose
We have been getting complaints from copr users that they are hitting
out of date cloudfront cached data when they are doing builds.
We are syncing not all that often currently, and sometimes if a updates
push or rawhide compose finishes after the sync time it coud be a long
while before it picks
On Wed, Mar 4, 2020 at 6:04 PM Kevin Fenzi wrote:
>
> We have been getting complaints from copr users that they are hitting
> out of date cloudfront cached data when they are doing builds.
> We are syncing not all that often currently, and sometimes if a updates
> push or rawhide compose finishes
We have been getting complaints from copr users that they are hitting
out of date cloudfront cached data when they are doing builds.
We are syncing not all that often currently, and sometimes if a updates
push or rawhide compose finishes after the sync time it coud be a long
while before it picks
On Wed, Mar 04, 2020 at 07:45:29AM -0500, Stephen John Smoogen wrote:
> On Wed, 4 Mar 2020 at 04:00, Julen Landa Alustiza
> wrote:
>
> > Is there an ETA for the next vacuum process? If we can wait for some
> >
>
> There is no ETA as it depends on the number of builds that have been done
> since
Hi all,
Last week during our weekly meeting we have discuss trying to better
prioritize our work and tickets. In order to do that we are going to try to
use a "yummy vs trouble" [1] index and use a prioritization matrix [0] to
order our work.
Yummy representing the added value or benefit of a
Dear all,
You are kindly invited to the meeting:
Fedora Infrastructure on 2020-03-05 from 15:00:00 to 16:00:00 UTC
At fedora-meetin...@irc.freenode.net
The meeting will be about:
Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day
before.
Source:
Great job addressing this Clément
On Mon, Mar 2, 2020 at 5:26 PM Clement Verna
wrote:
> Hi all,
>
> An XSS vulnerability was reported against Bodhi, I have patched the
> staging and production instances [0][1] until I get the fix upstream and
> deploy a new release.
>
> [0] -
>
On Wed, 4 Mar 2020 at 04:00, Julen Landa Alustiza
wrote:
> Is there an ETA for the next vacuum process? If we can wait for some
>
There is no ETA as it depends on the number of builds that have been done
since the last autovac. A large number means it is further into the future
but takes much
Is there an ETA for the next vacuum process? If we can wait for some
months it might worth to upgrade to newer rhel and postgres after dc
migration but before next autovacuum process instead of lowering now the
max age and forcing another autovacuum process with current old postgres
20/3/4
On Tue, 3 Mar 2020 at 22:39, Kevin Fenzi wrote:
> And our lazyness and indecision pays off!
>
> The autovac is finally done and load should be back to normal.
>
Should we lower down the autovacuum max age ? so that next times it runs it
does not take that long ?
>
> I am going to re-enable
11 matches
Mail list logo
