Hi Cyril,
On Fri, Jan 11, 2019 at 12:35:12AM +0100, Cyril Bonté wrote:
> Well, from what I've seen with a small test, I've a different conclusion
> about the commit which introduced the issue. It looks to have been
> introduced earlier with commit 0108bb3e4 "MEDIUM: mailers: Init alerts
> during
Hi
we are getting error while extracting tar file 1.8.17 on windows
error screen shot attched in mail
[image: image.png]
--
Thanks & Regards,
Girish
--
Hi all,
Le 08/01/2019 à 10:06, Willy Tarreau a écrit :
On Tue, Jan 08, 2019 at 09:31:22AM +0100, Frederic Lecaille wrote:
Indeed this script could worked with a short mailer timeout before af4021e6
commit. Another git bisect shows that 53216e7d introduced the email bombing
issue.
Note that
Hi Pieter,
On Thu, Jan 10, 2019 at 08:05:47PM +0100, PiBa-NL wrote:
> Hi Johan, Olivier, Willy,
>
> Op 10-1-2019 om 17:00 schreef Johan Hendriks:
> > I just updated to 1.9.1 on my test system.
> >
> > We noticed that when a server fails we now get tons of mail, and with
> > tons we mean a lot.
Hi Johan, Olivier, Willy,
Op 10-1-2019 om 17:00 schreef Johan Hendriks:
I just updated to 1.9.1 on my test system.
We noticed that when a server fails we now get tons of mail, and with
tons we mean a lot.
After a client backend server fails we usually get 1 mail on 1.8.x now
with 1.9.1 within
Willy,
Am 10.01.19 um 19:40 schrieb Willy Tarreau:
> Conclusion : the affected status is only temporary and enough to go
> once the backport is done. This simply means we don't need a "fixed-1.9"
> or whatever, we just have to remove the "affected" label exactly as it
> would have been if the
Hi Tim,
On Thu, Jan 10, 2019 at 04:12:54PM +0100, Tim Düsterhus wrote:
> > I tend to think that if labels already mark the relevance to a branch,
> > then they override the status and probably we don't really care about
> > the status. The "moby" project above does that by the way, with
> >
I just updated to 1.9.1 on my test system.
We noticed that when a server fails we now get tons of mail, and with
tons we mean a lot.
After a client backend server fails we usually get 1 mail on 1.8.x now
with 1.9.1 within 1 minute we have the following.
mailq | grep -B2 l...@testdomain.nl |
Aleks,
Am 10.01.19 um 15:30 schrieb Aleksandar Lazic:
> In general I also see a huge benefit to add a issue tracker I also know
> that's a
> workflow change for the developers.
>
> As I also follow the discussion let suggest me the following.
>
> * add some templates for the different cases e.
Willy,
Am 09.01.19 um 15:22 schrieb Willy Tarreau:
>> Here's some more recent projects that probably grew up with GitHub. I
>> can't comment how they do the backports, though:
>>
>> https://github.com/nodejs/node/issues (has LTS / Edge)
>> https://github.com/zfsonlinux/zfs/issues (has stable /
Am 09.01.2019 um 15:22 schrieb Willy Tarreau:
> Hi Tim,
>
> On Wed, Jan 09, 2019 at 12:58:30PM +0100, Tim Düsterhus wrote:
>> Am 09.01.19 um 05:31 schrieb Willy Tarreau:
>>> Except that the "naturally" part here is manually performed by someone,
>>> and an issue tracker is nothing more than an
11 matches
Mail list logo
