• anonymous (3/3) Feb 18 2015 I just saw that an issue I'm subscribed to was commented on hours
• Brad Roberts via Digitalmars-d (5/8) Feb 18 2015 Hrm.. that'd be my job. I just looked and there's a little shy of 1000
• David Eagen (3/4) Feb 18 2015 Brad, thanks for keeping the infrastructure running.
• David Eagen (5/9) Feb 18 2015 What I meant to say was that as an admin myself I know how
• ketmar (5/8) Feb 18 2015 maybe if you will not able to find the cause of mail overflow, a little=...
• Brad Roberts via Digitalmars-d (3/11) Feb 18 2015 I appreciate the offer, but I don't need the help. It just currently
• ketmar (2/4) Feb 18 2015 ah, that's good. so one thing less to do for me. ;-)=
• Martin Nowak (5/6) Feb 18 2015 That was apparently cause by me updating the 2.067 branches.
• Brad Roberts via Digitalmars-d (2/9) Feb 18 2015
• Jacob Carlborg (5/8) Feb 20 2015 So that's way I've seen over 300 issues updated in the newsgroup and

"anonymous" <anonymous example.com> writes:

I just saw that an issue I'm subscribed to was commented on hours 
ago, but no email from Bugzilla yet. They usually arrive 
instantly. Maybe some gears got stuck on the server?

Brad Roberts via Digitalmars-d <digitalmars-d puremagic.com> writes:

Hrm.. that'd be my job.  I just looked and there's a little shy of 1000 
messages queued up to go out.  I'm digging in to see if I can tell why 
the queue running stopped running.

The backlog is flowing out now.

On 2/18/2015 5:24 AM, anonymous via Digitalmars-d wrote:
 I just saw that an issue I'm subscribed to was commented on hours ago,
 but no email from Bugzilla yet. They usually arrive instantly. Maybe
 some gears got stuck on the server?

"David Eagen" <davideagen mailinator.com> writes:

On Wednesday, 18 February 2015 at 23:51:29 UTC, Brad Roberts 
wrote:
 Hrm.. that'd be my job.

Brad, thanks for keeping the infrastructure running.

"David Eagen" <davideagen mailinator.com> writes:

On Thursday, 19 February 2015 at 01:02:48 UTC, David Eagen wrote:
 On Wednesday, 18 February 2015 at 23:51:29 UTC, Brad Roberts 
 wrote:
 Hrm.. that'd be my job.

 Brad, thanks for keeping the infrastructure running.

What I meant to say was that as an admin myself I know how 
critical things like this are and how there is no spotlight and 
praise for when things go well. It's only when things break that 
attention turns to the admins. :)

ketmar <ketmar ketmar.no-ip.org> writes:

On Wed, 18 Feb 2015 15:51:14 -0800, Brad Roberts via Digitalmars-d wrote:

 Hrm.. that'd be my job.  I just looked and there's a little shy of 1000
 messages queued up to go out.  I'm digging in to see if I can tell why
 the queue running stopped running.

maybe if you will not able to find the cause of mail overflow, a little=20
cron script that checks if there is too much mail queued and sends an=20
XMPP/direct mail message can help? i'm not a server guy, but if you need=20
some helping hand with script, you can tell me.=

Brad Roberts via Digitalmars-d <digitalmars-d puremagic.com> writes:

On 2/18/2015 5:04 PM, ketmar via Digitalmars-d wrote:
 On Wed, 18 Feb 2015 15:51:14 -0800, Brad Roberts via Digitalmars-d wrote:

 Hrm.. that'd be my job.  I just looked and there's a little shy of 1000
 messages queued up to go out.  I'm digging in to see if I can tell why
 the queue running stopped running.

 maybe if you will not able to find the cause of mail overflow, a little
 cron script that checks if there is too much mail queued and sends an
 XMPP/direct mail message can help? i'm not a server guy, but if you need
 some helping hand with script, you can tell me.

I appreciate the offer, but I don't need the help.  It just currently 
has nothing monitoring it.  Easy enough to do.

ketmar <ketmar ketmar.no-ip.org> writes:

On Wed, 18 Feb 2015 17:10:48 -0800, Brad Roberts via Digitalmars-d wrote:

 I appreciate the offer, but I don't need the help.  It just currently
 has nothing monitoring it.  Easy enough to do.

ah, that's good. so one thing less to do for me. ;-)=

Martin Nowak <code+news.digitalmars dawg.eu> writes:

On 02/19/2015 12:51 AM, Brad Roberts via Digitalmars-d wrote:
 I just looked and there's a little shy of 1000 messages queued up to go out.

That was apparently cause by me updating the 2.067 branches.
I probably should have deleted and recreated it instead, but I didn't 
knew how the mails are generated.
You have some sort of github hook that gets called for each added commit?

Brad Roberts via Digitalmars-d <digitalmars-d puremagic.com> writes:

github has built-in bugzilla integration which does all that.

On 2/18/2015 6:23 PM, Martin Nowak via Digitalmars-d wrote:
 On 02/19/2015 12:51 AM, Brad Roberts via Digitalmars-d wrote:
 I just looked and there's a little shy of 1000 messages queued up to
 go out.

 That was apparently cause by me updating the 2.067 branches.
 I probably should have deleted and recreated it instead, but I didn't
 knew how the mails are generated.
 You have some sort of github hook that gets called for each added commit?

Jacob Carlborg <doob me.com> writes:

On 2015-02-19 03:23, Martin Nowak wrote:

 That was apparently cause by me updating the 2.067 branches.
 I probably should have deleted and recreated it instead, but I didn't
 knew how the mails are generated.

So that's way I've seen over 300 issues updated in the newsgroup and 
commit messages which seems to contain already merged pull requests.

-- 
/Jacob Carlborg