Re: [sagemath-admins] Re: [sage-devel] Trac Error

2020-07-08 Thread William Stein
There were 27GB of apache error and access logs going back years, so I deleted them: 15M trac_sagemath_org-error.log.1593388800 14M trac_sagemath_org-error.log.1593475200 16M trac_sagemath_org-error.log.1593561600 17M trac_sagemath_org-error.log.1593648000 14M trac_sagemath_org

Re: [sagemath-admins] Re: [sage-devel] Trac Error

2020-07-08 Thread William Stein
I'll figure out how to fix this right now. On Wed, Jul 8, 2020 at 12:49 PM Dima Pasechnik wrote: > > oh, "no space left on device". > > anyone? I am a.f.k. > > On Wed, 8 Jul 2020, 20:34 'Reimundo Heluani' via sage-devel, > wrote: >> >> I am getting the following error trying to generate a merge

Re: [sage-devel] Trac Error

2020-07-08 Thread Dima Pasechnik
oh, "no space left on device". anyone? I am a.f.k. On Wed, 8 Jul 2020, 20:34 'Reimundo Heluani' via sage-devel, < sage-devel@googlegroups.com> wrote: > I am getting the following error trying to generate a merge on trac, it > looks > like a full disk? > > Failure to create temporary git reposito

[sage-devel] Trac Error

2020-07-08 Thread 'Reimundo Heluani' via sage-devel
I am getting the following error trying to generate a merge on trac, it looks like a full disk? Failure to create temporary git repository clone for merge preview of cbd2319dd12d941deede5b1550e6e5b686f2468a: Cloning into '/tmp/tmpCL92Zh'... done. error: unable to write file build/pkgs/rw/distr

[sage-devel] trac error again

2018-06-19 Thread 'Martin R' via sage-devel
if I recall correctly, there was a similar issue recently, but I don't know how it was fixed. This time it concerns https://trac.sagemath.org/ticket/25606 Martin -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group an

Re: [sage-devel] Trac error on push

2016-10-31 Thread François Bissey
On 01/11/16 07:31, jhonrubia6 wrote: Thank you. Is there any place where is documented how to get the new ssh key for the host whenever this happens again? I don't know that's published anywhere at the present time. Anyone? Francois -- You received this message because you are subscribed to t

Re: [sage-devel] Trac error on push

2016-10-31 Thread jhonrubia6
Thank you. Is there any place where is documented how to get the new ssh key for the host whenever this happens again? El lunes, 31 de octubre de 2016, 8:54:29 (UTC+1), François escribió: > > Add > trac.sagemath.org,104.197.143.230 ecdsa-sha2-nistp256 > E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzd

Re: [sage-devel] Trac error on push

2016-10-31 Thread Marco Cognetta
That worked. Thanks again. On Monday, October 31, 2016 at 4:54:29 PM UTC+9, François wrote: > > Add > trac.sagemath.org,104.197.143.230 ecdsa-sha2-nistp256 > E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBG+/AO490umZWuczUgClP4BgFm5XR9I43z4kf9f+pu8Uj6UvH/7Pz1oBkJ71xET+xTmecBHB2c9OwlgPjB70AB

Re: [sage-devel] Trac error on push

2016-10-31 Thread Francois Bissey
Add trac.sagemath.org,104.197.143.230 ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBG+/AO490umZWuczUgClP4BgFm5XR9I43z4kf9f+pu8Uj6UvH/7Pz1oBkJ71xET+xTmecBHB2c9OwlgPjB70AB8= as a single line at the end of .ssh/know_hosts François > On 31/10/2016, at 20:52, Marco Cognetta

Re: [sage-devel] Trac error on push

2016-10-31 Thread Marco Cognetta
There is no longer a line with trac.sagemath.org but when I try to connect I do not get the option of adding it to the list of known_hosts. I had this problem a few weeks ago and was able to fix it but I have forgotten how... Thanks for your help thus far! On Monday, October 31, 2016 at 4:36:35

Re: [sage-devel] Trac error on push

2016-10-31 Thread Francois Bissey
Then, it may have been the wrong host. You should remove the line starting with trac.sagemath.org Once removed, the next time you connect to the trac server, you will be asked about adding it to the list of know_hosts. François > On 31/10/2016, at 20:27, Marco Cognetta wrote: > > I have done t

Re: [sage-devel] Trac error on push

2016-10-31 Thread Marco Cognetta
I have done that but I still get the same error. How do I get the correct information to put in known_hosts? On Monday, October 31, 2016 at 4:14:23 PM UTC+9, François wrote: > > Removing the 4th line in your file > ~/.ssh/known_hosts > looks like it would do the trick. > I think it would be th

Re: [sage-devel] Trac error on push

2016-10-31 Thread Francois Bissey
Removing the 4th line in your file ~/.ssh/known_hosts looks like it would do the trick. I think it would be the 4th line but it could be another one. It will almost certainly be another one for other people. François > On 31/10/2016, at 20:10, Marco Cognetta wrote: > > What is the fix for this

Re: [sage-devel] Trac error on push

2016-10-31 Thread Marco Cognetta
What is the fix for this? I have tried getting the updated trac and testing my rsa keys. On Saturday, October 29, 2016 at 2:33:05 AM UTC+9, Dima Pasechnik wrote: > > > > On Friday, October 28, 2016 at 5:01:54 PM UTC, jhonrubia6 wrote: >> >> Is not 104.197.143.230? >> >> >> OnoSendaiII:sage J_Honr

Re: [sage-devel] Trac error on push

2016-10-28 Thread Dima Pasechnik
On Friday, October 28, 2016 at 5:01:54 PM UTC, jhonrubia6 wrote: > > Is not 104.197.143.230? > > > OnoSendaiII:sage J_Honrubia$ host trac.sagemath.org > > trac.sagemath.org has address 104.197.143.230 > the IP might have remained, but the (virtual) machine got changed, and got SSH keys regener

Re: [sage-devel] Trac error on push

2016-10-28 Thread jhonrubia6
Is not 104.197.143.230? OnoSendaiII:sage J_Honrubia$ host trac.sagemath.org trac.sagemath.org has address 104.197.143.230 El jueves, 27 de octubre de 2016, 20:29:30 (UTC+2), John Cremona escribió: > > The machine hosting trac did change recently. > > On 27 October 2016 at 19:17, jhonrubia

Re: [sage-devel] Trac error on push

2016-10-27 Thread John Cremona
The machine hosting trac did change recently. On 27 October 2016 at 19:17, jhonrubia6 wrote: > After working on ticket #21052, I committed the changed file and tried to > git trac push and get the error > > git_trac.git_error.GitError: git returned with non-zero exit code (128) when > executing "

[sage-devel] Trac error on push

2016-10-27 Thread jhonrubia6
After working on ticket #21052, I committed the changed file and tried to git trac push and get the error git_trac.git_error.GitError: git returned with non-zero exit code (128) when executing "git push trac HEAD:refs/heads/u/jhonrubia6/add_pictures_to_implicit_plot3d_py" STDERR: @

[sage-devel] Trac error: branch shows entire file deleted

2016-07-20 Thread Paul Masson
When I look at the branch for ticket #15134 it show the entire file hyperbolic.py deleted. For Travis it shows just the changes from the existing commits as expected. He also says the error occurs sometimes. Any idea what causes this? It's a bit disconcerting to see the contents of an entire fi

[sage-devel] Trac error

2015-05-21 Thread Jori Mäntysalo
http://trac.sagemath.org/ticket/17018 --> Trac detected an internal error: OSError: [Errno 2] No such file or directory: '/tmp/tmpTo_W1D' I think that trac error page should have an email address of it's maintainer. Compare for example to ServerAdmin at Apache configuration. -- Jori Mäntysal

[sage-devel] trac error, disk full?

2014-05-24 Thread Ralf Stephan
Hi, the "View Tickets" page says: *Error: Macro TicketQuery(type=defect,format=count) failed* could not write block 1 of temporary file: No space left on device HINT: Perhaps out of disk space? http://trac.sagemath.org/wiki/TicketReports Regards, -- You received this message because you are

[sage-devel] trac error: out of disk space?

2010-05-15 Thread Minh Nguyen
Hi folks, On IRC, Florent Hivert reported that the Sage trac is reporting the following error when clicking on the link "Timeline": Opened and closed tickets event provider (TicketModule) failed: ProgrammingError: could not write block 1 of temporary file: No space left on device HINT: Perhaps ou

[sage-devel] Trac error.

2009-10-13 Thread Dr David Kirkby
See below for the error message {6} All Tickets By Milestone (Including closed) A more complex example to show how to make advanced reports. Report execution failed: column "modified" does not exist LINE 16: (CASE status WHEN 'closed' THEN modified ELSE (-1)*p... ^ Dave --~--~-~--~