[sage-devel] Re: puzzling dev.upload_ssh_key() in developer manual
Hello, I think removing that content from the doc isn't the solution. I thinking we should work on a feature like this yet it has proof of being useful so it justify its need. Thank you, -- 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] Re: Regression introduced by #21670 ?
I created https://trac.sagemath.org/ticket/21712 for this issue On Saturday, October 15, 2016 at 10:15:35 PM UTC+2, Salvatore Stella wrote: > > Dear All, > it seems that the ticket #21670 recently merged into develop makes sage > crash > on my machine, can anyone replicate this? > > In a new xterm run this: > > $ echo "a = 1" > /tmp/test.py > $ sage > ┌┐ > │ SageMath version 7.4.rc2, Release Date: 2016-10-15 │ > │ Type "notebook()" for the browser-based notebook interface.│ > │ Type "help()" for help.│ > └┘ > ┏┓ > ┃ Warning: this is a prerelease version, and it may be unstable. ┃ > ┗┛ > sage: > > now resize the xterm, everything works as it is supposed to. > now attach /tmp/test.py and again resize the window. I get this: > > sage: %attach /tmp/prova.py > sage: > > > ** > > Oops, Sage crashed. We do our best to make it stable, but... > > A crash report was automatically generated with the following information: > - A verbatim copy of the crash traceback. > - A copy of your input history during this session. > - Data on your current Sage configuration. > > It was left in the file named: > '/home/VulK/.sage/ipython-5.0.0/Sage_crash_report.txt' > If you can email this file to the developers, the information in it will > help > them in understanding and correcting the problem. > > You can mail it to: sage-support at sage-s...@googlegroups.com > > with the subject 'Sage Crash Report'. > > If you want to do it now, the following command will work (under Unix): > mail -s 'Sage Crash Report' sage-s...@googlegroups.com < > /home/VulK/.sage/ipython-5.0.0/Sage_crash_report.txt > > To ensure accurate tracking of this issue, please file a report about it > at: > http://trac.sagemath.org > > Hit to quit (your terminal may close): > > > > I attached to this e-mail the crash report. > > Best > S. > > -- 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] Regression introduced by #21670 ?
Dear All,
it seems that the ticket #21670 recently merged into develop makes sage crash
on my machine, can anyone replicate this?
In a new xterm run this:
$ echo "a = 1" > /tmp/test.py
$ sage
┌┐
│ SageMath version 7.4.rc2, Release Date: 2016-10-15 │
│ Type "notebook()" for the browser-based notebook interface.│
│ Type "help()" for help.│
└┘
┏┓
┃ Warning: this is a prerelease version, and it may be unstable. ┃
┗┛
sage:
now resize the xterm, everything works as it is supposed to.
now attach /tmp/test.py and again resize the window. I get this:
sage: %attach /tmp/prova.py
sage:
**
Oops, Sage crashed. We do our best to make it stable, but...
A crash report was automatically generated with the following information:
- A verbatim copy of the crash traceback.
- A copy of your input history during this session.
- Data on your current Sage configuration.
It was left in the file named:
'/home/VulK/.sage/ipython-5.0.0/Sage_crash_report.txt'
If you can email this file to the developers, the information in it will help
them in understanding and correcting the problem.
You can mail it to: sage-support at sage-supp...@googlegroups.com
with the subject 'Sage Crash Report'.
If you want to do it now, the following command will work (under Unix):
mail -s 'Sage Crash Report' sage-supp...@googlegroups.com <
/home/VulK/.sage/ipython-5.0.0/Sage_crash_report.txt
To ensure accurate tracking of this issue, please file a report about it at:
http://trac.sagemath.org
Hit to quit (your terminal may close):
I attached to this e-mail the crash report.
Best
S.
--
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.
***
IPython post-mortem report
{'commit_hash': u'1ba246d',
'commit_source': 'installation',
'default_encoding': 'UTF-8',
'ipython_path': '/mnt/sage/local/lib/python2.7/site-packages/IPython',
'ipython_version': '5.0.0',
'os_name': 'posix',
'platform':
'Linux-4.1.12-gentoo-x86_64-Intel-R-_Core-TM-_i7-5600U_CPU_@_2.60GHz-with-gentoo-2.2',
'sys_executable': '/mnt/sage/local/bin/python',
'sys_platform': 'linux2',
'sys_version': '2.7.10 (default, Oct 15 2016, 20:24:20) \n[GCC 4.9.3]'}
***
***
Crash traceback:
---
---
error Python 2.7.10: /mnt/sage/local/bin/python
Sat Oct 15 22:13:36 2016
A problem occurred executing Python code. Here is the sequence of function
calls leading up to the error, with the most recent (innermost) call last.
/mnt/sage/src/bin/sage-ipython in ()
1 #!/usr/bin/env python
2 # -*- coding: utf-8 -*-
3 """
4 Sage IPython startup script.
5 """
6
7 from sage.repl.interpreter import SageTerminalApp
8
9 app = SageTerminalApp.instance()
10 app.initialize()
---> 11 app.start()
global app.start = >
/mnt/sage/local/lib/python2.7/site-packages/IPython/terminal/ipapp.pyc in
start(self=)
333 if self.log_level <= logging.INFO: print()
334
335 def _pylab_changed(self, name, old, new):
336 """Replace --pylab='inline' with --pylab='auto'"""
337 if new == 'inline':
338 warnings.warn("'inline' not available as pylab backend, "
339 "using 'auto' instead.")
340 self.pylab = 'auto'
341
342 def start(self):
343 if self.subapp is not None:
344 return self.subapp.start()
345 # perform any prexec steps:
346 if self.interact:
347 self.log.debug("Starting IPython's mainloop...")
--> 348 self.shell.mainloop()
self.shell.mainloop = >
349 else:
350 self.log.debug("IPython not
[sage-devel] Re: puzzling dev.upload_ssh_key() in developer manual
here is the ready for review docs fix: https://trac.sagemath.org/ticket/21710 On Saturday, October 15, 2016 at 6:46:33 PM UTC, Dima Pasechnik wrote: > > Does anyone have an idea what > > sage: dev.upload_ssh_key() > > in > http://doc.sagemath.org/html/en/developer/trac.html#generating-and-uploading-your-ssh-keys > is meant to do? Is it something related to the retired dev scripts? > If yes, this section has to be removed. This command is not working anyway. > > 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] Re: puzzling dev.upload_ssh_key() in developer manual
On Saturday, October 15, 2016 at 6:58:44 PM UTC, Travis Scrimshaw wrote: > > It was suppose to put your ssh key onto your trac account automatically > (and generate one if you had none). I found it to be very useful. I suspect > it broke when the trac server IP(?) changed. > No, I think it is gone, as sagedev is gone. See https://trac.sagemath.org/ticket/20645 Here is the ready for review ticket fixing this part of docs: https://trac.sagemath.org/ticket/21710 > > Best, > Travis > > > On Saturday, October 15, 2016 at 1:46:33 PM UTC-5, Dima Pasechnik wrote: >> >> Does anyone have an idea what >> >> sage: dev.upload_ssh_key() >> >> in >> http://doc.sagemath.org/html/en/developer/trac.html#generating-and-uploading-your-ssh-keys >> is meant to do? Is it something related to the retired dev scripts? >> If yes, this section has to be removed. This command is not working >> anyway. >> >> 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] Re: puzzling dev.upload_ssh_key() in developer manual
It was suppose to put your ssh key onto your trac account automatically (and generate one if you had none). I found it to be very useful. I suspect it broke when the trac server IP(?) changed. Best, Travis On Saturday, October 15, 2016 at 1:46:33 PM UTC-5, Dima Pasechnik wrote: > > Does anyone have an idea what > > sage: dev.upload_ssh_key() > > in > http://doc.sagemath.org/html/en/developer/trac.html#generating-and-uploading-your-ssh-keys > is meant to do? Is it something related to the retired dev scripts? > If yes, this section has to be removed. This command is not working anyway. > > 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] puzzling dev.upload_ssh_key() in developer manual
Does anyone have an idea what sage: dev.upload_ssh_key() in http://doc.sagemath.org/html/en/developer/trac.html#generating-and-uploading-your-ssh-keys is meant to do? Is it something related to the retired dev scripts? If yes, this section has to be removed. This command is not working anyway. 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.
