Thank you! But the problem for me is that the terminal don't start.
On Wednesday, January 7, 2015 at 11:04:20 PM UTC-5, kcrisman wrote:
On Wednesday, January 7, 2015 7:57:36 PM UTC-5, Ruizhi Deng wrote:
I'm a new comer to Sage and I'm running sage on my mac with OS X 10.10. I
started sage
I reinstalled sage on my computer, but it still doesn't work.
On Wednesday, January 7, 2015 at 7:57:36 PM UTC-5, Ruizhi Deng wrote:
I'm a new comer to Sage and I'm running sage on my mac with OS X 10.10. I
started sage successfully for the first time but I have trouble running
sage after
Do you mean that if you open Sage.app and click on the Terminal Session
Sage menu, that Terminal.app doesn’t open? Or do you mean that
Terminal.app doesn’t open automatically when you try to start the notebook
server?
For now, doing it manually once (and typing in a password) should fix the
Hi
On 8 January 2015 at 14:32, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
On 2015-01-08 06:36, Jan Groenewald wrote:
I get about one zero sized users.pickle 2-3 times per week.
Really, how does that happen? I am also running a sagenb server on my
university and this never happened.
It
I posted trac #17610 which is ready for review. It now tries starting it in a
Terminal if it fails for any reason. This should be more robust to any sort of
corruption, and also help show the problem in the cases where it does fail.
-Ivan
On Jan 8, 2015, at 5:17 PM, Ivan Andrus
On 2015-01-08 06:36, Jan Groenewald wrote:
I get about one zero sized users.pickle 2-3 times per week.
Really, how does that happen? I am also running a sagenb server on my
university and this never happened.
In any case, I hope that this issue will be fixed by
I only changed the way the buildbot builds the binary release. The new
binary is not on the web page yet, but should be soon.
On Thursday, January 8, 2015 6:10:33 AM UTC+1, Robert McBroom wrote:
Fixes to the source files?
On Tuesday, January 6, 2015 3:23:10 AM UTC-5, Volker Braun wrote:
Only 2 years later, and I found a way around segmentation faults due to
memory problems. It seems that my looping functions fill up memory over
time
and lead to segmentation faults at random stages. I now define such
functions using the @fork decorator and then they don't seem to
I get about one zero sized users.pickle 2-3 times per week.
Really, how does that happen? I am also running a sagenb server on my
university and this never happened.
In any case, I hope that this issue will be fixed by
https://github.com/sagemath/sagenb/pull/287
For completeness -
