On Sat, Aug 17, 2013 at 2:19 PM, Brian Wolff <bawolff(a)gmail.com> wrote:
Lets not point fingers at specific people. Its really
unhelpful and causes
defensiveness.
In the case of gitblit, the problem at this point has been identified (web
spiders DOSing us accidentally). Its really not surprising that creating
zip files ~100mb on the fly is expensive. It doesn't really seem that
likely that a stack trace would help solve such a problem, and really its
more a config issue on our end than a problem with gitblit.
I really don't see anything wrong with what any of the wmf folks did on
that bug.
To be honest, I don't feel like the git browser for WMF has ever been truly
stable. The ops team does their best, but I think it's just the nature of
the application. Git wasn't really made to be accessed that kind of way,
and here who knows how many people are using that service daily.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
www.whizkidztech.com | tylerromeo(a)gmail.com