On Debian testing running on core i7 + 16 GB RAM, upgrading 9.2.beta7
configured for use of all possible system libraries an runningptestlong
gets me the same transient an same three permanent failures already reported for 9.2.beta7
and 9.2.beta5
:
sage -t --long --warn-long 175.4 --random-seed=0 src/sage/tests/parigp.py # Timed out
sage -t --long --warn-long 175.4 --random-seed=0 src/sage/rings/complex_arb.pyx # 6 doctests failed
sage -t --long --warn-long 175.4 --random-seed=0 src/sage/tests/gap_packages.py # 1 doctest failed
sage -t --long --warn-long 175.4 --random-seed=0 src/sage/rings/real_arb.pyx # 2 doctests failed
HTH,
Damn !
This release breaks sage-shell-mode
support for a sage session into emacs. After starting an emacs session, I get the normal banner and a normal prompt. A little while after that (about 0.5 to 1 second), a warning WARNING: your terminal doesn't support cursor position requests (CPR).
appears immediately below the banner and above the prompt, then the cursor goes right to the right margin (i. e. in the right scrollbar).
I still can type Sage code, which appears at the left margin on the line immediately below the prompt. Typing <Return>
displays a continuation prompt (.....:
) 7 spaces,, then my code,which gets executed and the answer printed on tjhe line below the continuation prompt. Example :
┌────────────────────────────────────────────────────────────────────┐
│ SageMath version 9.2.beta8, Release Date: 2020-08-10 │
│ Using Python 3.7.3. Type "help()" for help. │
└────────────────────────────────────────────────────────────────────┘
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Warning: this is a prerelease version, and it may be unstable. ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
WARNING: your terminal doesn't support cursor position requests (CPR).
sage: sage:
....: 1+1
2
sage:
No error message appears in the terminal window from which I launched emacs
; nothing unusual in the *Messages*
buffer either.
I’m stymied…
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-r...@googlegroups.com.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-r...@googlegroups.com.
Further bad news : this also somehow breaks the communication between emacs
and sage
:
quit
in the sage
session never returns ; you have to kill
emacs
to get your damn prompt back…
Any attempt to use sage
from an org-mode
document never returns : same issue…
HTH,
John, what is your current emacs
version ?
It's version 26.3. I also just quit emacs and restarted, and now I'm having the same problems you were having. Modifying 'src/bin/sage' to accept a '--simple-prompt'
I do not know how to re-open a closed ticket...
I could compile Sage 9.2.beta 8 on Mac OS.10.15.6 and run sage. Quitting sage has evoked no problem…But, for ptestlong, it has some errors. I don’t know whether this is completely local porblem…
As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html415221a9a8 (trac/develop, tag: 9.2.beta8) Updated SageMath version to 9.2.beta8
--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/81a3cb4a-ebd9-44a7-a3d0-bcdf1afeb566o%40googlegroups.com.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-r...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/81a3cb4a-ebd9-44a7-a3d0-bcdf1afeb566o%40googlegroups.com.
>
>
> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-r...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-r...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/d87277ae-08bd-44a8-81a5-960b9c383192o%40googlegroups.com.
On Thu, 13 Aug 2020, 20:03 John H Palmieri, <jhpalm...@gmail.com> wrote:
On Thursday, August 13, 2020 at 11:44:59 AM UTC-7, Samuel Lelievre wrote:I opened a ticket for the issue reported by John:- Fix building html documentation on macOSI tried applying #30345 but the problem persisted.Then I realised Dima mentioned #30345 in relation totimeouts when running make testalllong on Debian,not in relation to the dochtml issue on macOS. : /Thank you for opening the ticket. Independently I had tried #30345 to see if it would fix the problem, but I also see the problem with "make doc-clean" followed by "./sage --docbuild all html", which should not be affected by #30345.#30345 matters if you set MAKE to "make -jX" for X>1
--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-r...@googlegroups.com.
OK, I tried to reproduce this on a Mac, and indeed the build hangs
waiting for some parallel process to finish:
On hitting ctrl-C, it always (the stage of the docbuild may differ though)
shows the following backtrace:
...
[dochtml] KeyboardInterrupt
--
You received this message because you are subscribed to the Google Groups "sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/06455f10-9dd7-435d-8f7e-17f22c0f8cbco%40googlegroups.com.
Damn !
This release breaks
sage-shell-mode
support for a sage session into emacs. After starting an emacs session, I get the normal banner and a normal prompt. A little while after that (about 0.5 to 1 second), a warningWARNING: your terminal doesn't support cursor position requests (CPR).
appears immediately below the banner and above the prompt, then the cursor goes right to the right margin (i. e. in the right scrollbar).I still can type Sage code, which appears at the left margin on the line immediately below the prompt. Typing
<Return>
displays a continuation prompt (.....:
) 7 spaces,, then my code,which gets executed and the answer printed on tjhe line below the continuation prompt. Example :┌────────────────────────────────────────────────────────────────────┐ │ SageMath version 9.2.beta8, Release Date: 2020-08-10 │ │ Using Python 3.7.3. Type "help()" for help. │ └────────────────────────────────────────────────────────────────────┘ ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ ┃ Warning: this is a prerelease version, and it may be unstable. ┃ ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ WARNING: your terminal doesn't support cursor position requests (CPR). sage: sage: ....: 1+1 2 sage:
No error message appears in the terminal window from which I launched
emacs
; nothing unusual in the*Messages*
buffer either.I’m stymied…
Le mardi 11 août 2020 13:39:38 UTC+2, Emmanuel Charpentier a écrit :On Debian testing running on core i7 + 16 GB RAM, upgrading
9.2.beta7
configured for use of all possible system libraries an runningptestlong
gets me the same transient an same three permanent failures already reported for9.2.beta7
and9.2.beta5
:sage -t --long --warn-long 175.4 --random-seed=0 src/sage/tests/parigp.py # Timed out sage -t --long --warn-long 175.4 --random-seed=0 src/sage/rings/complex_arb.pyx # 6 doctests failed sage -t --long --warn-long 175.4 --random-seed=0 src/sage/tests/gap_packages.py # 1 doctest failed sage -t --long --warn-long 175.4 --random-seed=0 src/sage/rings/real_arb.pyx # 2 doctests failed
HTH,
Le mardi 11 août 2020 00:51:35 UTC+2, Volker Braun a écrit :
As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html
With Neovim as editor, the same warning appears in its builtin terminal, followed by some error messages that break the REPL. Luckily, upgrading Neovim from 0.2.2 to 0.4.3 fixed it on my end.
Done. I haven't figured out the sage-shell customizations so that it automatically uses '--simple-prompt' whenever you ask it to start Sage, but that's a separate problem.
On Tuesday, August 11, 2020 at 9:44:15 AM UTC-7, Emmanuel Charpentier wrote:
Le mardi 11 août 2020 18:38:00 UTC+2, John H Palmieri a écrit :It's version 26.3. I also just quit emacs and restarted, and now I'm having the same problems you were having. Modifying 'src/bin/sage' to accept a '--simple-prompt'option and then using that seems to work.On Tuesday, August 11, 2020 at 9:32:20 AM UTC-7, Emmanuel Charpentier wrote:John, what is your current
emacs
version ?
Le mardi 11 août 2020 18:26:04 UTC+2, John H Palmieri a écrit :I had no experience with sage-shell-mode until about 5 minutes ago, but it works for me, except for some weird artifacts when it reprints what I typed at the command line:
┌────────────────────────────────────────────────────────────────────┐
│ SageMath version 9.2.beta8, Release Date: 2020-08-10 │
│ Using Python 3.7.3. Type "help()" for help. │
└────────────────────────────────────────────────────────────────────┘
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Warning: this is a prerelease version, and it may be unstable. ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
sage: Sq(3)
SSSqqq(((333)))))))))
Sq(3)
sage: Sq(3)*Sq(4)
SSSSqqqq((((3333))))****SSSSqqqq((((4444))))))))))))
Sq(7)
sage: quit()
qqqqquuuuuiiiiittttt((((()))))))))))))))
Exiting Sage (CPU time 0m0.31s, Wall time 0m47.95s).
Process Sage finishedOn Tuesday, August 11, 2020 at 9:20:00 AM UTC-7, Emmanuel Charpentier wrote:Further bad news : this also somehow breaks the communication between
emacs
andsage
:
quit
in thesage
session never returns ; you have tokill
emacs
to get your damn prompt back…Any attempt to use
sage
from anorg-mode
document never returns : same issue…HTH,