2018-03-12 00:58:51 +0200 | received badge | ● Notable Question (source) |
2017-10-06 23:37:28 +0200 | received badge | ● Teacher (source) |
2017-10-06 23:37:28 +0200 | received badge | ● Self-Learner (source) |
2017-10-06 23:37:28 +0200 | received badge | ● Necromancer (source) |
2017-10-06 23:37:11 +0200 | received badge | ● Nice Question (source) |
2017-10-05 15:33:58 +0200 | answered a question | Build Error when Uploading Notebooks in Sage It seems this is a current and reproducible bug. The report is here. Until this is fixed, it might not be wise to import .zip files in the sagenb gui if you intend to use the Notebook Exporter to convert them into Jupyter notebook files in Sage 8.0. (Although I have no idea how widespread the problem is, in my case the Notebook Exporter is not obviously recoverable, at least without a reinstallation.) Two workarounds are:
|
2017-10-04 04:34:33 +0200 | commented question | Build Error when Uploading Notebooks in Sage Apologies for the delay; for some reason I'm not receiving email alerts from this thread, so I missed your last comment until I went looking, but I'll go ahead and submit it now that I know it's of interest. |
2017-10-04 04:33:12 +0200 | received badge | ● Popular Question (source) |
2017-08-21 16:50:45 +0200 | commented question | Build Error when Uploading Notebooks in Sage Importing a zipped collection in the GUI of sagenb triggers an "internal error" (the build error in the text above). Restarting sage AFTER the internal error and then running sage -n gets me to the Notebook Exporter, which is then inoperable with it's own "internal error" (and the big box of errors at the end of my post). The notebook exporter has been inoperable ever since (I had to use a different VM to hack my eventual export to Jupyter), but interestingly, I just realized that both the sagenb GUI and Jupyter start fine. So whatever internal error importing in the sagenb causes only is problematic when I run Notebook Exporter afterward. (Weird!) If others post with a similar error, I'll submit a bug report; for now, I'll move on out of respect for everyone's (volunteer) time. Thanks! |
2017-08-21 15:22:08 +0200 | received badge | ● Student (source) |
2017-08-20 22:08:38 +0200 | commented question | Build Error when Uploading Notebooks in Sage Thanks, I'm aware, and thanks for taking a look. I was hoping to import old notebooks from an old server, then export them to the Jupyter (as needed/wanted), but I've given up at this point. I'll add for the benefit of anyone in a similar situation in the future that I finally just manually copied the files containing my old notebooks into Sage notebook's standard location on the new server, just long enough to export them to Jupiter, as kcrisman suggests. This avoided the need for an "import", but wouldn't be a long term fix if I wanted to continue to use the old Sage notebook server, as copying files without "importing" them messes with Sage's counter of the number of created notebooks. |
2017-08-07 23:10:42 +0200 | asked a question | Build Error when Uploading Notebooks in Sage Running Fedora 26 as a virtual machine, I recently installed Sage 8.0 from source (and was thrilled to see support for Jupiter....amazing!). Besides a minor error coming from Open SSL which I'll try to run down later, Sage seems to work perfectly, until I try to upload one or more zipped notebook files into the Sage Notebook. On screen, after uploading, I get a non descriptive "500:internal error" message. In the terminal, I get the message "Build Error:Could not build url for endpoint 'home' with values ['username']. Did you mean 'worksheet_listing.home' instead?" If the notebook is a new notebook (one which I didn't just download from Sage and reimport for diagnostic purposes) clicking on "continue" allows me to see and interact with the new notebooks. However, if I then exit Sage and restart it and the notebook, I get a 500:internal error in both the sage and jupiter notebooks and nothing else displayed (no link to "continue" to the notebooks or anything else). In the terminal I get a much longer error, which I've copied at the end of my message. Does anyone have any suggestions as to where to start trying to fix this? I've searched the forum, and not seen similar errors, but maybe I missed something. (I read that for a while Sage had import errors with files containing nonascii characters, so I'll add that I can recreate this behavior using a file called "Test" with the single line "1+1" contained in it, as well as using files exported from both a Sage 8.0 server and an older server I am still running.) Any advice would be greatly appreciated! (Longer error follows here:) |