Re: [sage-devel] Re: Patchbot troubles
This was due to the trac change. I've updated the patchbot to understand the this (and it's actually much cleaner as there are csv/tsv formats now so I don't have to parse the html). It'll take a while to actually update all the tickets in question. On Thu, Jul 25, 2013 at 2:32 AM, David Loeffler d.a.loeff...@warwick.ac.uk wrote: Some further data: the problem is definitely with the patchbot server process running at patchbot.sagemath.org -- if you request a list of all tickets with http://patchbot.sagemath.org/ticket/?status=allorder=idrawpretty then it really does return all tickets, but for the majority of them, it claims the ticket status is unknown. David On Thursday, July 25, 2013 12:28:26 AM UTC+2, David Loeffler wrote: Hi folks, I'm at SD51 in Leiden this week, and it would be nice if we had a working sage patchbot to test the patches we're writing... At the moment there seems to be something rather odd going on with the patchbot. I have set a patchbot worker process running on one of our Warwick machines, but it seems to ignore most of the needs-review / positive-review patches, and instead skips to testing some ancient ones that are marked as needs-work or needs-info. Poking around in the code, it seems that the worker process runs through the list of tickets returned by the database query http://patchbot.sagemath.org/ticket/?rawstatus=open This query only returns 241 tickets (while we actually have several thousand tickets open) and this list seems to only contain 10 of the 400 or so that are needs_review / positive_review. What's going on here? Is it just that the patchbot got hopelessly broken by the recent trac server update and nobody's tried to fix it yet? It does seem to be getting some live data from the trac server (the data returned includes ticket modification times, some of which are in the last few hours) but it's clearly somehow ignoring most of the tickets it should be returning. Can anyone diagnose what's causing this? David -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Sage preparser not robust against typos
Hey William,
On Thursday, July 25, 2013 8:27:21 PM UTC+5:30, Volker Braun wrote:
The problem is that exceptions raised by the inputsplitter are not handled
by IPython. I've asked at IPython-devel at
http://python.6.x6.nabble.com/InputSplitter-and-SyntaxError-td5025938.htmlbut
didn't get an answer so far.
That said, in this particular case:
preparse('R.t = QQ{]')
outputs something that looks like a bug in the preparser implementation:
...
opening = constructor.rindex('[')
ValueError: substring not found
If anything, it should be raising a SyntaxError, right?
William
In my hack patch, I change this to a syntax error (although I probably
should catch any exception and convert it to a SyntaxError). However by
raising *any* (standard) exception in the inputsplitter, it is not caught
by IPython and so it gets viewed as a Sage crash as per Volker's statement.
Best,
Travis
--
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Patchbot troubles
Hi Robert, That's excellent -- thanks! One question: there are some tickets (e.g. #14366) where it is not picking up correctly information in the ticket comments specifying which patches to apply. Is it possible that this part of the patchbot's code has also been broken by the trac update? (I suppose this will become moot soon anyway when we switch to git) David On 26 July 2013 08:26, Robert Bradshaw rober...@gmail.com wrote: This was due to the trac change. I've updated the patchbot to understand the this (and it's actually much cleaner as there are csv/tsv formats now so I don't have to parse the html). It'll take a while to actually update all the tickets in question. On Thu, Jul 25, 2013 at 2:32 AM, David Loeffler d.a.loeff...@warwick.ac.uk wrote: Some further data: the problem is definitely with the patchbot server process running at patchbot.sagemath.org -- if you request a list of all tickets with http://patchbot.sagemath.org/ticket/?status=allorder=idrawpretty then it really does return all tickets, but for the majority of them, it claims the ticket status is unknown. David On Thursday, July 25, 2013 12:28:26 AM UTC+2, David Loeffler wrote: Hi folks, I'm at SD51 in Leiden this week, and it would be nice if we had a working sage patchbot to test the patches we're writing... At the moment there seems to be something rather odd going on with the patchbot. I have set a patchbot worker process running on one of our Warwick machines, but it seems to ignore most of the needs-review / positive-review patches, and instead skips to testing some ancient ones that are marked as needs-work or needs-info. Poking around in the code, it seems that the worker process runs through the list of tickets returned by the database query http://patchbot.sagemath.org/ticket/?rawstatus=open This query only returns 241 tickets (while we actually have several thousand tickets open) and this list seems to only contain 10 of the 400 or so that are needs_review / positive_review. What's going on here? Is it just that the patchbot got hopelessly broken by the recent trac server update and nobody's tried to fix it yet? It does seem to be getting some live data from the trac server (the data returned includes ticket modification times, some of which are in the last few hours) but it's clearly somehow ignoring most of the tickets it should be returning. Can anyone diagnose what's causing this? David -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: New Trac Server
Hey Andrew, I believe there's a minor bug with the new trac server: the names in the replying to get the same markup as the ticket number. In particular, if a ticket is closed, they names will have a strikeout through them. Ex. http://trac.sagemath.org/ticket/14031. Or is this the expected behavior? Best, Travis On Monday, July 22, 2013 12:17:12 AM UTC+5:30, R. Andrew Ohana wrote: Yup, this is again the issue of needing more space on the trac server. I cleared out some more stuff while we continue to wait to get some more disk space on the system. On Sun, Jul 21, 2013 at 7:41 AM, Travis Scrimshaw tsc...@ucdavis.edujavascript: wrote: Hey Andrew, Somethings wrong with the new trac server: OperationalError: could not extend file base/30560/30652: No space left on device HINT: Check free disk space. I get this by going to view tickets - tickets needing review. I also get an error message on the view tickets page in the Bugs subheader and trying to view other larger groups of tickets. Best, Travis -- 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+...@googlegroups.com javascript:. To post to this group, send email to sage-...@googlegroups.comjavascript: . Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. -- Andrew -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Trying to build 5.11.beta3 using cygwin64
Hey everyone (especially cygwin people),
I've been trying for the past 2 hours to build sage 5.11.beta3 on
cygwin64, however it continuously fails when building zlib. I've
multiple-checked that I've installed all of the dependencies (and
overkilled on some of them too), and I've installed zlib ver 1.2.8 directly
on cygwin, although sage installation doesn't seem recognize it (same
version). Any idea on how to get this to work? I've tried rebasing,
deleting the partial installation, deleting the entire build. I'm running
off a Windows Vista home premium OS. Below is the relavent portion of the
log file. Any help is greatly appreciated.
Thank you,
Travis
make[2]: Leaving directory `/home/Travis/sage-5.11.beta3/spkg'
env SAGE_BUILD_TOOLCHAIN=yes make -j2 toolchain
make[2]: Entering directory `/home/Travis/sage-5.11.beta3/spkg'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
make[2]: Nothing to be done for `toolchain'.
make[2]: Leaving directory `/home/Travis/sage-5.11.beta3/spkg'
make -j2 toolchain-deps
make[2]: Entering directory `/home/Travis/sage-5.11.beta3/spkg'
make[2]: warning: -jN forced in submake: disabling jobserver mode.
make -j2 /home/Travis/sage-5.11.beta3/spkg/installed/zlib-1.2.8
make[3]: Entering directory `/home/Travis/sage-5.11.beta3/spkg'
make[3]: warning: -jN forced in submake: disabling jobserver mode.
/home/Travis/sage-5.11.beta3/spkg/pipestatus sage-spkg ${SAGE_SPKG_OPTS}
zlib-1 .2.8 21 tee -a
/home/Travis/sage-5.11.beta3/logs/pkgs/zlib-1.2.8.log
Found package zlib-1.2.8 in spkg/standard/zlib-1.2.8.spkg
zlib-1.2.8
Extracting package
/home/Travis/sage-5.11.beta3/spkg/standard/zlib-1.2.8.spkg
-rwxr-xr-x 1 Administrators None 532210 Jun 6 01:26
/home/Travis/sage-5.11.beta 3/spkg/standard/zlib-1.2.8.spkg
Finished extraction
Host system:
CYGWIN_NT-6.0 Travis-Notebook 1.7.22(0.268/5/3) 2013-07-22 17:06 x86_64
Cygwin
C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-cygwin/4.8.1/lto-wrapper.exe
Target: x86_64-pc-cygwin
Configured with: /usr/src/ports/gcc/gcc-4.8.1-1/src/gcc-4.8.1/configure
--srcdir =/usr/src/ports/gcc/gcc-4.8.1-1/src/gcc-4.8.1 --prefix=/usr
--exec-prefix=/usr - -bindir=/usr/bin --sbindir=/usr/sbin
--libexecdir=/usr/lib --datadir=/usr/share --localstatedir=/var
--sysconfdir=/etc --datarootdir=/usr/share --docdir=/usr/sh are/doc/gcc -C
--build=x86_64-pc-cygwin --host=x86_64-pc-cygwin --target=x86_64- pc-cygwin
--without-libiconv-prefix --without-libintl-prefix --enable-shared --e
nable-shared-libgcc --enable-static --enable-version-specific-runtime-libs
--ena ble-bootstrap --disable-__cxa_atexit --with-dwarf2
--with-tune=generic --enable- languages=c,c++,fortran,lto,objc,obj-c++
--enable-graphite --enable-threads=posi x --enable-libatomic
--enable-libgomp --disable-libitm --enable-libquadmath --en
able-libquadmath-support --enable-libssp --enable-libgcj-sublibs
--disable-java- awt --disable-symvers
--with-ecj-jar=/usr/share/java/ecj.jar --with-gnu-ld --wit h-gnu-as
--with-cloog-include=/usr/include/cloog-isl --without-libiconv-prefix -
-without-libintl-prefix --with-system-zlib
Thread model: posix
gcc version 4.8.1 (GCC)
make[4]: Entering directory
`/home/Travis/sage-5.11.beta3/spkg/build/zlib-1.2.8/
src'
gcc -O3 -Wall -c -o adler32.o adler32.c
gcc -O3 -Wall -c -o compress.o compress.c
gcc -O3 -Wall -c -o crc32.o crc32.c
gcc -O3 -Wall -c -o deflate.o deflate.c
gcc -O3 -Wall -c -o gzclose.o gzclose.c
gcc -O3 -Wall -c -o gzlib.o gzlib.c
gzlib.c: In function ‘gz_open’:
gzlib.c:256:9: warning: implicit declaration of function ‘lseek’
[-Wimplicit-fun ction-declaration]
state-start = LSEEK(state-fd, 0, SEEK_CUR);
^
gcc -O3 -Wall -c -o gzread.o gzread.c
gzread.c: In function ‘gz_load’:
gzread.c:30:9: warning: implicit declaration of function ‘read’
[-Wimplicit-func tion-declaration]
ret = read(state-fd, buf + *have, len - *have);
^
gzread.c: In function ‘gzclose_r’:
gzread.c:591:5: warning: implicit declaration of function ‘close’
[-Wimplicit-fu nction-declaration]
ret = close(state-fd);
^
gcc -O3 -Wall -c -o gzwrite.o gzwrite.c
gcc -O3 -Wall -c -o infback.o infback.c
gzwrite.c: In function ‘gz_comp’:
gzwrite.c:84:9: warning: implicit declaration of function ‘write’
[-Wimplicit-fu nction-declaration]
got = write(state-fd, strm-next_in, strm-avail_in);
^
gzwrite.c: In function ‘gzclose_w’:
gzwrite.c:573:5: warning: implicit declaration of function ‘close’
[-Wimplicit-f unction-declaration]
if (close(state-fd) == -1)
^
gcc -O3 -Wall -c -o inffast.o inffast.c
gcc -O3 -Wall -c -o inflate.o inflate.c
gcc -O3 -Wall -c -o inftrees.o inftrees.c
gcc -O3 -Wall -c -o trees.o trees.c
Re: [sage-devel] Re: Patchbot troubles
On Fri, Jul 26, 2013 at 3:19 AM, David Loeffler d.a.loeff...@warwick.ac.uk wrote: Hi Robert, That's excellent -- thanks! One question: there are some tickets (e.g. #14366) where it is not picking up correctly information in the ticket comments specifying which patches to apply. Is it possible that this part of the patchbot's code has also been broken by the trac update? For some reason there were some extra (unprinted) characters hanging on the end of that line in the comment. Specifically, utf-8 encoded http://unicode-table.com/en/search/?q=200b http://trac.sagemath.org/ticket/14366?format=rss Search for Fri, 26 Jul 2013 09:55:29 to see your comment. No idea how they got here, when I added the same comment I saw nothing. (Did you copy and paste this from somewhere?) (I suppose this will become moot soon anyway when we switch to git) Yes! On 26 July 2013 08:26, Robert Bradshaw rober...@gmail.com wrote: This was due to the trac change. I've updated the patchbot to understand the this (and it's actually much cleaner as there are csv/tsv formats now so I don't have to parse the html). It'll take a while to actually update all the tickets in question. On Thu, Jul 25, 2013 at 2:32 AM, David Loeffler d.a.loeff...@warwick.ac.uk wrote: Some further data: the problem is definitely with the patchbot server process running at patchbot.sagemath.org -- if you request a list of all tickets with http://patchbot.sagemath.org/ticket/?status=allorder=idrawpretty then it really does return all tickets, but for the majority of them, it claims the ticket status is unknown. David On Thursday, July 25, 2013 12:28:26 AM UTC+2, David Loeffler wrote: Hi folks, I'm at SD51 in Leiden this week, and it would be nice if we had a working sage patchbot to test the patches we're writing... At the moment there seems to be something rather odd going on with the patchbot. I have set a patchbot worker process running on one of our Warwick machines, but it seems to ignore most of the needs-review / positive-review patches, and instead skips to testing some ancient ones that are marked as needs-work or needs-info. Poking around in the code, it seems that the worker process runs through the list of tickets returned by the database query http://patchbot.sagemath.org/ticket/?rawstatus=open This query only returns 241 tickets (while we actually have several thousand tickets open) and this list seems to only contain 10 of the 400 or so that are needs_review / positive_review. What's going on here? Is it just that the patchbot got hopelessly broken by the recent trac server update and nobody's tried to fix it yet? It does seem to be getting some live data from the trac server (the data returned includes ticket modification times, some of which are in the last few hours) but it's clearly somehow ignoring most of the tickets it should be returning. Can anyone diagnose what's causing this? David -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: UTF-8 and old terminals (new startup banner)
At the very least, lets be careful to avoid fancy invisible unicode characters: https://groups.google.com/forum/#!topic/sage-devel/LjC75cae7XI On Thu, Jul 25, 2013 at 9:52 PM, William Stein wst...@gmail.com wrote: On Mon, Jul 8, 2013 at 2:05 PM, Robert Bradshaw rober...@math.washington.edu wrote: On Mon, Jul 8, 2013 at 1:55 AM, Julien Puydt julien.pu...@laposte.net wrote: Le 08/07/2013 10:51, Nils Bruin a écrit : On Monday, July 8, 2013 4:05:29 AM UTC+2, Volker Braun wrote: Frédéric Chapoton has written a patch at http://trac.sagemath.org/14733 http://trac.sagemath.org/14733 that will beautify the Sage startup banner using some UTF-8 characters to draw the box. This will display incorrectly in terminals that do not support UTF-8. In that case, Sage still works but the box around the banner is garbled (most likely rendered by placeholder signs for non-ASCII characters). -1 to a UTF-8 banner. There's hardly anything in the sage command line that requires a UTF-8 capable terminal (all the colour stuff should shut off automatically for a dumb terminal). Why require it for *just* the banner? More personally, I dislike the UTF-8 banner because it looks too nice. To me it doesn't fit with the simple prompt-and-return-value interface (see banners of magma, maple, R, matlab, pari/GP, python, IPython, GAP, Singular). The graphics looking lines are more suggestive of a menu-driven interface to me, like the text-based dialog interfaces. So to me, the +-|-built borders raise expectations more appropriate for what sage command line offers. -1 too for the same reasons. Keep the banner short and simple ; people don't come to sage to enjoy that sight! I agree, no need to have fancy unicode here. If you're doing something that requires nice output you should probably be using a notebook interface anyways; the CLI interface just isn't going to go there and going part way is worse than just keeping things simple. I used the patch, and I think it is beautiful. I completely disagree with the comments such as I dislike the UTF-8 banner because it looks too nice. and Keep the banner short and simple ; people don't come to sage to enjoy that sight!Clean beauty is exactly what people (at least me!) want in software. The banner in Sage right now, which I probably wrote (?), looks frankly ugly and like a hack, compared to the one on this patch. Also, UTF is clearly the future of strings, having native default support in modern interpreters, editors, etc., and also being critical to supporting users who aren't using English. This patch is along the same lines as the recent inclusion of a nice color prompt (thanks Volker) in that it makes Sage prettier and more pleasant to use. So my strong vote *for* this ticket. Moreover, I like it so much I'll be henceforth applying it to the standard system-wide version of Sage at https://cloud.sagemath.com, even if it doesn't get into Sage. In particular, I disagree with If you're doing something that requires nice output you should probably be using a notebook interface anyways -- since the terminal interface *is* part of the notebook interface now, and it must look nice. -- William -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out. -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: UTF-8 and old terminals (new startup banner)
Although (perhaps?) surprising, some languages don't have spaces and require zero-width space to designate word boundaries for line breaks. On Friday, July 26, 2013 3:02:41 PM UTC-4, Robert Bradshaw wrote: At the very least, lets be careful to avoid fancy invisible unicode characters: https://groups.google.com/forum/#!topic/sage-devel/LjC75cae7XI -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
