Thanks! I actually fixed my problem now. There was something broken with my
openssl installation. Sorry for the noise!
Best,
Anne
On Friday, April 28, 2017 at 12:13:25 PM UTC-7, Volker Braun wrote:
>
> Did you run that from within UC Davis? There is quite a number of academic
> networks that s
Did you run that from within UC Davis? There is quite a number of academic
networks that subscribe to the "if we filter out ICMP at the network border
we can't be hacked" fallacy. A better test would be:
$ ssh g...@trac.sagemath.org
PTY allocation request failed on channel 0
hello vbraun, this
I am sorry if I posted in the wrong thread (should I open a new one?).
But for me this still does not work. I cannot even ping trac:
ping sine.math.ucdavis.edu
PING sine.math.ucdavis.edu (169.237.99.79): 56 data bytes
64 bytes from 169.237.99.79: icmp_seq=0 ttl=57 time=13.852 ms
64 bytes from 169
On Fri, Apr 28, 2017 at 12:49 PM, Kwankyu Lee wrote:
> Hi,
>
> For the remote origin, the usual configuration is
>
> [remote "origin"]
> url = git://github.com/sagemath/sage.git
> fetch = +refs/heads/*:refs/remotes/origin/*
>
> If the same fetch setting is used for the remote trac, then the git cl
Hi,
For the remote origin, the usual configuration is
[remote "origin"]
url = git://github.com/sagemath/sage.git
fetch = +refs/heads/*:refs/remotes/origin/*
If the same fetch setting is used for the remote trac, then the git client
would try to download all heads from the trac.
I confess th
Did it ever starting working for you again, Anne? I'm not seeing any
problems here.
For what it's worth, before anyone else asks, the original problem
that this thread was about had to do with a badly behaving web scraper
that was causing a DOS on the Trac website itself--this would not
impact gi
On Friday, April 28, 2017 at 4:59:48 AM UTC+1, Anne Schilling wrote:
>
> I just tried
>
> git fetch origin
> fatal: unable to connect to trac.sagemath.org:
> trac.sagemath.org[0: 104.197.143.230]: errno=Operation timed out
>
worked for me now (~3 hours later).
>
> Is this related?
>
> Anne
>
I just tried
git fetch origin
fatal: unable to connect to trac.sagemath.org:
trac.sagemath.org[0: 104.197.143.230]: errno=Operation timed out
Is this related?
Anne
On Saturday, April 22, 2017 at 12:21:29 PM UTC-7, Michael Orlitzky wrote:
>
> On 04/21/2017 05:30 AM, Erik Bray wrote:
> >>
> >>
On 04/21/2017 05:30 AM, Erik Bray wrote:
Does this mean that we need some robots.txt somewhere, perhaps after some
restructuring,
which would protect expensive resources from this sort of overload?
There already is a robots.txt and this host was not respecting it.
If this becomes a bigger p
On Thu, Apr 20, 2017 at 9:10 PM, Dima Pasechnik wrote:
>
>
> On Thursday, April 20, 2017 at 4:04:19 PM UTC+1, Erik Bray wrote:
>>
>> On Thu, Apr 20, 2017 at 4:54 PM, Dima Pasechnik wrote:
>> >
>> >
>> > On Thursday, April 20, 2017 at 3:38:12 PM UTC+1, Erik Bray wrote:
>> >>
>> >> Just posting to
Hi,
On Thu, Apr 20, 2017 at 12:10:42PM -0700, Dima Pasechnik wrote:
> >
> > Strange, well, I created a firewall rule blocking that IP for now and
> > everything seems to be fine.
> >
>
> Does this mean that we need some robots.txt somewhere, perhaps after some
> restructuring,
> which would pr
On Thursday, April 20, 2017 at 4:04:19 PM UTC+1, Erik Bray wrote:
>
> On Thu, Apr 20, 2017 at 4:54 PM, Dima Pasechnik > wrote:
> >
> >
> > On Thursday, April 20, 2017 at 3:38:12 PM UTC+1, Erik Bray wrote:
> >>
> >> Just posting to say I've noticed and am investigating.
> >>
> >> It seems
On Thursday, April 20, 2017 at 9:25:12 AM UTC-7, Daniel Krenn wrote:
>
> On 2017-04-20 17:09, John H Palmieri wrote:
> > Since some time last night, I have been unable to use "git trac checkout
> > TICKET":
>
> This (other ticket) worked for me about an hour ago.
>
Yes, you're right. It's ju
On 2017-04-20 17:09, John H Palmieri wrote:
> Since some time last night, I have been unable to use "git trac checkout
> TICKET":
This (other ticket) worked for me about an hour ago.
Daniel
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To uns
Since some time last night, I have been unable to use "git trac checkout
TICKET":
$ git trac checkout 22764
Loading ticket #22764...
Checking out Trac #22764 remote branch
fb90d5e3667237f2d9fc7ba982b466bc52802b1d -> local branch
t/22764/fb90d5e3667237f2d9fc7ba982b466bc52802b1d...
Traceback (mos
On Thu, Apr 20, 2017 at 4:54 PM, Dima Pasechnik wrote:
>
>
> On Thursday, April 20, 2017 at 3:38:12 PM UTC+1, Erik Bray wrote:
>>
>> Just posting to say I've noticed and am investigating.
>>
>> It seems that somebody is performing a scrape of the front page which
>> includes a list of users on the
On Thursday, April 20, 2017 at 3:38:12 PM UTC+1, Erik Bray wrote:
>
> Just posting to say I've noticed and am investigating.
>
> It seems that somebody is performing a scrape of the front page which
> includes a list of users on the site [1] each of which is a link to a
> search query for all
No, it seems to have been resolved for some time now.
On Mon, Jun 13, 2016 at 2:34 PM Eric Gourgoulhon
wrote:
> It's OK for me (from Paris). Do you still have any issue?
>
> Eric.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
It's OK for me (from Paris). Do you still have any issue?
Eric.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post
19 matches
Mail list logo
