Re: [sage-devel] Sage runs in Window's 10's new Unix subsystem

2016-12-26 Thread GK
After some windows update, it does not work for me anymore... :( Sage starts, the notebook loads, but once I try to do anything (i.e. create a new worksheet or open an existing one) I get a server error (on the browser) and some '[Errno 12] Cannot allocate memory' on the terminal. As suggested

[sage-devel] threejs as standard package

2016-12-26 Thread Andrey Novoseltsev
Hello, How about making threejs a standard package? It was optional for a while, used in SageMathCell to power its own version of threejs viewer. https://trac.sagemath.org/ticket/12402 has added threejs as possible output for a bunch of backends and ideally it will become standard for all inte

Re: [sage-devel] Re: Problems Authenticating to Trac Server with Public Key

2016-12-26 Thread Dima Pasechnik
a reliable way to check that one got a ssh key is to run ssh-keygen -l -f on it. Does your patch do this? (hopefully you saved that interesting wrong key somewhere) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group an

Re: [sage-devel] patchbot quasar timeouts and coverage-plugin

2016-12-26 Thread Vincent Delecroix
quasar might timeout (and not the others) because it is installed with a lot of optional packages (basically all minus the one that cause trouble). The relevant optional tests might be, I will test later on sage: g = graphs.LocalMcLaughlinGraph(); g Local McLaughlin Graph: Graph on 162 vertices

Re: [sage-devel] Re: Problems Authenticating to Trac Server with Public Key

2016-12-26 Thread Erik Bray
On Dec 26, 2016 10:04 AM, "Erik Bray" wrote: Okay, I fixed it. Someone had uploaded some invalid keys and the regeneration of authorized_keys was failing. I confirmed, after removing the invalid keys, that authorized_keys was regenerated and includes Maxie's keys. Sorry for the trouble. When

Re: [sage-devel] Re: Problems Authenticating to Trac Server with Public Key

2016-12-26 Thread Erik Bray
Okay, I fixed it. Someone had uploaded some invalid keys and the regeneration of authorized_keys was failing. I confirmed, after removing the invalid keys, that authorized_keys was regenerated and includes Maxie's keys. Sorry for the trouble. When I get back I'll have to see how the unsupported

Re: [sage-devel] Re: Problems Authenticating to Trac Server with Public Key

2016-12-26 Thread Erik Bray
On Mon, Dec 26, 2016 at 9:40 AM, Erik Bray wrote: > On Dec 26, 2016 09:28, "Erik Bray" wrote: > > On Dec 25, 2016 19:11, "Dima Pasechnik" wrote: > > > > On Sunday, December 25, 2016 at 12:31:27 PM UTC, Volker Braun wrote: >> >> The ~/.gitolite/logs/ may have some clues about what is going on...

Re: [sage-devel] Re: Problems Authenticating to Trac Server with Public Key

2016-12-26 Thread Erik Bray
On Dec 26, 2016 09:28, "Erik Bray" wrote: On Dec 25, 2016 19:11, "Dima Pasechnik" wrote: On Sunday, December 25, 2016 at 12:31:27 PM UTC, Volker Braun wrote: > > The ~/.gitolite/logs/ may have some clues about what is going on... > no, it doesn't, IMHO. Further, there are two (almost)copies

Re: [sage-devel] Re: Problems Authenticating to Trac Server with Public Key

2016-12-26 Thread Erik Bray
On Dec 25, 2016 19:11, "Dima Pasechnik" wrote: On Sunday, December 25, 2016 at 12:31:27 PM UTC, Volker Braun wrote: > > The ~/.gitolite/logs/ may have some clues about what is going on... > no, it doesn't, IMHO. Further, there are two (almost)copies of keystore/, one in ~/.gitolite/, and the