Mark,
On 6/12/2018 11:13 PM, Mark Thomas wrote:
You were banned for > 100,000 page views in a 24 hour period. That is
way more than any reasonably behaving client should be issuing.
I suspect you were pulling down one svn commit at a time. With the ASF
repo, that is pretty much guaranteed t
On 13/06/2018 01:33, Igal Sapir wrote:
On 6/12/2018 3:33 PM, Olaf Kock wrote:
On 12.06.2018 23:33, Igal Sapir wrote:
Perhaps it to revisit the thresholds that trigger warnings/bans. The
Tomcat SVN repo might be much larger today than it was when those
were last examined and set.
You might
On 6/12/2018 3:33 PM, Olaf Kock wrote:
On 12.06.2018 23:33, Igal Sapir wrote:
Perhaps it to revisit the thresholds that trigger warnings/bans. The
Tomcat SVN repo might be much larger today than it was when those
were last examined and set.
You might want to start at https://github.com/apache
On 12.06.2018 23:33, Igal Sapir wrote:
Perhaps it to revisit the thresholds that trigger warnings/bans. The
Tomcat SVN repo might be much larger today than it was when those were
last examined and set.
You might want to start at https://github.com/apache/tomcat instead of
pulling down SVN
Update:
On 6/12/2018 11:55 AM, Igal Sapir wrote:
According to Mark in that thread [1], there is a daily threshold and
if you exceed it you get a warning. "If you trigger three warnings in
a period" you get banned for a long term (weeks).
I did not see any warnings. The process failed with
On 6/12/2018 11:41 AM, Igal Sapir wrote:
The last thing I was trying to do was a complete SVN pull with 'git
svn clone' of Tomcat, which failed mid-process with 'error: git-svn
died of signal 11'. A google search shows results with the title
"[INFRA-10509] Can't connect to SVN - banned? - A
Hi all,
I am experiencing a weird network issue and as of ~48 hours ago I can
not connect to the Apache.org network. I am connected via AT&T Fiber
and spent half the day on the phone with them in vain. Unfortunately it
is not simple to get a new IP from AT&T (even though it is supposedly a
