I think this was actually a problem with autosave we had for about one week. Of course we didn't know that at the time. I'm not sure why to say, except the root problem is probably solved, and if not there is a straightforward way to just use plain jupyter in SMC anyways.
On Tuesday, November 15, 2016, Stan <schym...@gmail.com> wrote: > OK, I just asked Thomas to send me the email thread about his problem with > SMC. His communication was with William Stein and Harald Schilly, and > related to lost bits of a jupyter notebook that were not even recoverable > using the revert button or the backup utility, plus bits started > disappearing or re-arranging again. On 4 November, Harald replied to him > with the following words: "Hi, this sounds like a real bug we have to fix. > Getting a history and collaboration working with jupyter notebooks is not > easy.", followed by a message by William Stein on the same day indicating > that a fix would require a major rewrite of Jupyter, and suggesting a > method to use standard Jupyter within SMC. Unfortunately, Thomas overlooked > that suggestion and didn't try it out. Still, the problem of disappearing > or re-arranged code cells within a worksheet reminds me of problems I used > to have with sagews, but I haven't experienced them with jupyter so far. If > this is a particular problem with jupyter notebooks within SMC, and if it > re-occurs, perhaps this way of using jupyter should be discouraged in > favour of using pure jupyter or jupyter kernels within Sage worksheets. If > instructions are available how to do this, I'd be happy to try it out. > > Cheers > Stan > > On Monday, November 14, 2016 at 4:49:50 PM UTC+1, William wrote: >> >> On Mon, Nov 14, 2016 at 6:21 AM, Stan <schy...@gmail.com> wrote: >> > Dear all, >> > >> > A student of mine has been using SMC because the sage appliance in >> > virtualbox did not appear very useful with the jupyter notebook. Now >> that he >> > encountered a critical bug in SMC (reported offline), he is back with >> the >> >> I'm not aware of this bug. I don't know of any critical bugs in SMC. >> There are exactly 22 known SMC *bugs*, which you can see listed here, >> all of which we plan to fix ASAP: >> >> https://github.com/sagemathinc/smc/issues?utf8=%E2%9C%93&q= >> is%3Aissue%20is%3Aopen%20label%3AI-bug%20sort%3Acreat >> ed-asc%20-label%3Ablocked >> >> On can also use SMC via docker on Windows, Linux and OS X, as explained >> here: >> >> https://github.com/sagemathinc/smc/blob/master/src/dev/docker/README.md >> >> I wish I could recommend the official sagemath docker images, but it >> looks like they haven't been updated in 6 months to 1 year ago? (What >> the heck?) >> >> https://hub.docker.com/u/sagemath/ >> >> >> William >> >> > sage appliance in VB but it is truly a nightmare. The installation >> > instructions are still specific for sagews, not jupyter, but we at >> least >> > managed to change the working directory to something he can access. >> What we >> > haven't managed, is to get out of the kiosk mode in chrome. There is no >> > obvious possibility of opening several tabs, no address bar to get back >> to >> > the directory page and no back button. This means that every time he >> wants >> > to go back, e.g. after downloading the worksheet, he has to restart the >> > virtual machine! I don't understand why chrome was chosen instead of >> > firefox, and I have no idea why it is set up in kiosk mode. Is there >> any >> > sensible way to productively work with the sage appliance using the now >> > standard jupyter notebook?? I'm sorry if my frustration shows in these >> > lines, I probably should have asked earlier, but I am wondering a bit >> if >> > those that created the sage appliance actually use it themselves. I >> don't, >> > which is why it never occurred to me how difficult to use it might be. >> > Thanks for your help! >> > >> > Cheers >> > Stan >> > >> > -- >> > 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. >> > To post to this group, send email to sage-...@googlegroups.com. >> > Visit this group at https://groups.google.com/group/sage-devel. >> > For more options, visit https://groups.google.com/d/optout. >> >> >> >> -- >> William (http://wstein.org) >> > -- > 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 > <javascript:_e(%7B%7D,'cvml','sage-devel%2bunsubscr...@googlegroups.com');> > . > To post to this group, send email to sage-devel@googlegroups.com > <javascript:_e(%7B%7D,'cvml','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. > -- Sent from my massive iPhone 6 plus. -- 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.
