You're correct. (I just uploaded a .sws file without problem.) I'm glad to see it's otherwise being reported.
On Thursday, October 5, 2017 at 5:55:42 AM UTC-4, Dima Pasechnik wrote: > > > > On Thursday, October 5, 2017 at 10:22:38 AM UTC+1, Angela Hicks wrote: >> >> There's some speculation this is related to: this post >> <https://groups.google.com/forum/#!topic/sage-devel/1cBRR4nfaqE> which >> seems not unreasonable, but I'll post the details here (at kcrisman's >> suggestion). >> >> I'm running Fedora 26 as a virtual machine, I recently installed Sage 8.0 >> from source. The installation worked great until I: >> >> 1) Uploaded a zipped file into the old sage notebook gui. >> > > Yes, indeed, this doesn't work with *.zip archives any more. :-( > https://github.com/sagemath/sagenb/issues/433 > > Does it work for you with individual *.sws files (the "original" sagenb > format)? > (this does work, I think) > > > >> This triggers a 500:internal error on screen >> and a "Build Error:Could not build url for endpoint 'home' with values >> ['username']. Did you mean 'worksheet_listing.home' instead?" on the >> command line. >> The error seems benign (can be ignored) until I >> 2) Restart sage >> 3) Start the new Notebook Exporter gui. >> The gui has no links (so is not useable), and the command line reports a >> much longer error, which is posted in entirety here >> <https://ask.sagemath.org/question/38486/build-error-when-uploading-notebooks-in-sage/?comment=38658#post-id-38658>, >> >> where I first reported the problem. >> Repeated restarts do not fix the problem, although after a single restart >> both the notebook gui and the jupiter gui work fine. I can consistently >> replicate the same steps if I start again with a new copy of the same >> virtual machine. I have not tried reinstalling sage to see if I can >> replicate the problem afterwards. >> >> In the linked post, someone pointed out that they assumed no one would >> continue using sagenb, so if it was triggering a problem, it might not >> affect very many. I'm not sure how widespread this problem is, but it's >> worth pointing out I seem to be triggering it by doing exactly what people >> will tend to do as they update their sage server to 8.0: First import old >> notebooks into sagenb, then use the Notebook Exporter to switch them to >> Jupyter. >> > -- 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.
