GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
It turns out that the problem is two extra quote marks, accidentally added last May when making some massive changes:
It also exposed a problem with the queue list for cells (look in the communication with the server and you'll see an extra request for cell status, cells are queued up twice for checking, once when the evaluate cell request is sent, and once upon successful response of the evaluate request:
Which one of these should update the queue_id_list? @rkirov or Mike Hansen, do you remember if there is a problem for the cell to listed as running upon successful return of the eval request (i.e., delete the two lines in this pull request)?
Fix user history caching so the log works.
Don't queue up a cell to be running until a successful return from th…
…e evaluation request is received.
(Before this patch, the cell was queued up twice. Now it is queued up once, upon a successful request.)
@kini: do you want to review this, or is this change already in?
It doesn't seem to be in yet. The code looks good to me. Do you want it in 0.9.0? Should we create a new feature-freeze branch or something?
Well, on the other hand this is a bugfix, so it should go into the release branch anyway... I'll merge it and make a new SPKG.
Merge pull request #40 from jasongrout/log
Fix the user history log
Yes, it should go in. It fixes a major complaint of William's (and it's a pretty easy fix too!)
I'm pretty sure this has been live on sagenb.org for a few months as well...
It's in the SPKG at trac #11080 now. And it may have been live on sagenb.org at some point, but it is not now - I just checked and the log isn't updating on sagenb.org worksheets, though there are old logs from March or so.
I just pulled the latest changes (including pagination, etc.) into sagenb.org and am restarting right now.
Okay, it should be live now.
Sagenb.org turns out to be completely unusably slow. The python process is pegged at 100% CPU ever since starting it (at least 10-15 minutes), and it's impossible to log in. I got a listing of displayed worksheets at one point, but that was it. It may not be this commit; it could be anything since 5f0e216.
Odd. I tested these commits and they worked fine on my own machine. But then again that's my own machine. Did you try git bisecting?
bisecting the major 90,000 account sagenb.org is something I can't do at the moment. I'll take a look at the commits mentioned later and see if I can spot anything.
I suspect either the pagination commit or Dan Drake's commit. I thought it odd that the one page I was able to pull up, the published worksheets page, indicated only 5 pages * 25 worksheets = 125 published worksheets. That's way too low.
I reverted back to before 5f0e216, sagenb.org is now responsive, so something definitely is fishy since that commit.