Re: [sage-devel] cysignal, python signal module, and alarm functions
On Sunday, December 25, 2016 at 8:22:33 PM UTC+1, Jeroen Demeyer wrote: > > On 2016-12-25 12:55, Jean-Pierre Flori wrote: > > > > > > On Sunday, December 25, 2016 at 10:32:11 AM UTC+1, Jeroen Demeyer wrote: > > > > On 2016-12-24 13:30, Jean-Pierre Flori wrote: > > > I just want to kill Magma > > > > M.quit() should work. > > > > Sure, but how do I trigger a call to M.quit() iin the middle of a long > > computation? > > ??? Didn't you answer this question yourself before? > > M = magma() # I only need an ephemeral Magma instance > try: > alarm(3600) > M(...) # potentially very long one shot computation > except AlarmInterrupt: > M.quit() > That does not work! First the AlarmInterrupt gets caught as a KeyboardInterrupt inside expect.py which softly interrupts Magma and watis for its prompt. And even when done it raises a KeyboardInterrupt and does not end up in the except clause... -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] cysignal, python signal module, and alarm functions
On 2016-12-25 12:55, Jean-Pierre Flori wrote: On Sunday, December 25, 2016 at 10:32:11 AM UTC+1, Jeroen Demeyer wrote: On 2016-12-24 13:30, Jean-Pierre Flori wrote: > I just want to kill Magma M.quit() should work. Sure, but how do I trigger a call to M.quit() iin the middle of a long computation? ??? Didn't you answer this question yourself before? M = magma() # I only need an ephemeral Magma instance try: alarm(3600) M(...) # potentially very long one shot computation except AlarmInterrupt: M.quit() -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Problems Authenticating to Trac Server with Public Key
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 other in /srv/trac/sage_trac/gitolite-admin/. The public key in question is in the latter, but not in the former. I just copied it by hand now, not sure if it has had any effect. (I am at loss to describe the design where the same data is stored in 3 different places... :-)) Dima -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] patchbot quasar timeouts and coverage-plugin
On at least two tickets I found TestsFailed 7.5.rc0 Ubuntu/16.04/x86_64/4.4.0-53-generic/quasar because of timeouts. At https://trac.sagemath.org/ticket/22064: sage -t --long src/sage/graphs/generators/smallgraphs.py # Timed out At https://trac.sagemath.org/ticket/21968: sage -t --long src/sage/modular/abvar/abvar.py # Timed out Not sure if everything is all right with this patchbot; or maybe the timeout can be manually specified or whatever... ;) Moreover, the coverage plugin reports: -- 7.5.rc0 +++ 7.5.rc0 + #21976 +Missing doctests in ext/interpreters/wrapper_cc.pyx: 0 / 2 = 0% +ext/interpreters/wrapper_cc.pyx: 0.0% (0 of 2) Which is weird, as on these tickets, this file was not changed at all. -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Problems Authenticating to Trac Server with Public Key
The ~/.gitolite/logs/ may have some clues about what is going on... -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] cysignal, python signal module, and alarm functions
On Sunday, December 25, 2016 at 10:32:11 AM UTC+1, Jeroen Demeyer wrote: > > On 2016-12-24 13:30, Jean-Pierre Flori wrote: > > I just want to kill Magma > > M.quit() should work. > Sure, but how do I trigger a call to M.quit() iin the middle of a long computation? -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Problems Authenticating to Trac Server with Public Key
On Sunday, December 25, 2016 at 1:58:40 AM UTC, Maxie Schmidt wrote: > > What other ways do you suggest I try? ssh-copy-id fails with the > same Permission denied (publickey) error. Is there another way to upload > keys to the trac server? > the only user-allowed way is via the web interface. Once a key gets entered there, it gets copied into a trac store. I can see your (updated) key in this store. The store itself is not used by the sshd to allow logins. There is a process that updates the file (authorized_keys file of the git user account) responsible for the latter. And this process does not want to copy your key from the store for the reason unknown (perhaps there is some blacklisting going on, I don't know). After learning how to use auditd, I found the process to be certain GCE-specific python script called manage_accounts. I have no idea whether any manual intervention is possible without breaking things. We are seriously out of luck here, as we have only very few people who know more details about this GCE-specific trac/git connection, and they are most probably either on vacation, or insanely busy (or both :-)). Perhaps a temporary way out for you would be to push your Sage branches to a github repo and let your trac tickets refer to these branches. Sorry for not being more helpful at this point. Dima -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] cysignal, python signal module, and alarm functions
On 2016-12-24 13:30, Jean-Pierre Flori wrote: I just want to kill Magma M.quit() should work. -- 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 to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
