is HG Bot stopped intentionally ?

[Brendan Cully]

The bot has updated the tickets in the 'not yet' list below.

On Wednesday, 03 June 2015 at 13:32, Matt Mackall wrote:
> On Wed, 2015-06-03 at 03:32 +0900, FUJIWARA Katsunori wrote:
> > There are some issues not replied by HG Bot, even though they are
> > already fixed by changes with "(issueID)" in their summary line.
> > 
> > For example, status of issues fixed in Mercurial 3.4.1 stable release
> > are shown below:
> > 
> >   replied by HG Bot:
> > 
> >   - http://bz.selenic.com/show_bug.cgi?id=4290 (2015-05-07 19:00:54 UTC)
> >   - http://bz.selenic.com/show_bug.cgi?id=4569 (2015-05-07 19:00:58 UTC)
> >   - http://bz.selenic.com/show_bug.cgi?id=4642 (2015-05-19 12:45:34 UTC)
> >   - http://bz.selenic.com/show_bug.cgi?id=4646 (2015-05-07 19:01:06 UTC)
> >   - http://bz.selenic.com/show_bug.cgi?id=4646 (2015-05-07 19:01:06 UTC)
> >   - http://bz.selenic.com/show_bug.cgi?id=4661 (2015-05-14 21:30:46 UTC)
> >   - http://bz.selenic.com/show_bug.cgi?id=4669 (2015-05-15 17:00:49 UTC)
> >   - http://bz.selenic.com/show_bug.cgi?id=4670 (2015-05-15 17:00:41 UTC)
> > 
> >   not yet:
> > 
> >   - http://bz.selenic.com/show_bug.cgi?id=4678
> >   - http://bz.selenic.com/show_bug.cgi?id=4680
> >   - http://bz.selenic.com/show_bug.cgi?id=4682 (*)
> >   - http://bz.selenic.com/show_bug.cgi?id=4683 (*)
> >   - http://bz.selenic.com/show_bug.cgi?id=4684
> >   - http://bz.selenic.com/show_bug.cgi?id=4690
> > 
> > (*) replied by "Yuya" human Bot around 2015-05-28 12:25 UTC :-) 
> > 
> > Is it intentional ?
> > 
> > Sorry, if I overlooked some threads about this article.
> 
> For future reference, you can find who's responsible for a given thing
> here:
> 
> https://mercurial.selenic.com/wiki/ProjectInfrastructure
> 
> In this case, it turns out to be a combination of:
> 
> - expired self-signed cert on the unadvertised 443 port of
> bz.selenic.com
> - bts bot using https to avoid plaintext password
> - upgrade to python2.7.9 on bot's server
> - no error code returned on bugzilla hook failure
> - no error messages mailed out
> 
> We've set up a hack to work around it but I'm hoping we can get the BTS
> moved over to the central server in the next few months, where we now
> have proper SSL.
>