Hi,
Thanks for the screenshot, which is *very* helpful. Your error report
was confusing before since you said the student "couldn't log in".
Actually, what is happening is that they login just fine, but
displaying the list of worksheets causes an internal server error. I
know -- the two both sound like the same thing, but to a developer
they are different.
Anyways, I can replicate the problem at least, and will surely fix it this week.
In the meantime, I know this is ugly, but the student can probably
view their worksheets by using URL's like this:
http://sfa.sagenb.org/home/harberae/0/
http://sfa.sagenb.org/home/harberae/1/
etc. (Note the number) -- there is one for each worksheet. This is a
hideous workaround, but it is something.
I'm going to look at trying to fix this right now. If I do, I'll send
a followup email.
William
-- William
>
> Keith
>
> -----Original Message-----
> From: sage-utmos...@googlegroups.com
> [mailto:sage-utmos...@googlegroups.com] On Behalf Of William Stein
> Sent: Monday, September 19, 2011 9:32 AM
> To: sage-utmos...@googlegroups.com
> Subject: Re: [UTMOST-TestSites] major Sage problem
>
> On Mon, Sep 19, 2011 at 6:28 AM, Keith Hubbard <hubb...@sfasu.edu> wrote:
>> Last week, three students couldn’t get into their accounts at all
>> because of “server error”. Today, I can’t access any on my worksheets
>> (though I can log in). They all come up with the same “internal server
> error”
>> (attached). I’ve tried two different Sage accounts (keithhubbardlp,
>> MTH233) and Chrome and Firefox.
>>
>>
>>
>> If this isn’t fixed, we may have to abandon the Sage experiment.
>
> It may be fixed now. Please test this and let me know whether it is
> fixed or not for you.
>
> Thanks! And, thanks again for your report of issues. The problem
> was caused when I migrated all the Sage notebook servers to a new computer
> with more fast disk space.
>
> -- William
>
>>
>>
>>
>> Keith
>>
>>
>
>
>
> --
> William Stein
> Professor of Mathematics
> University of Washington
> http://wstein.org
>
--
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
I don't know. But I think I just fixed it.
If anybody has trouble with this "can't display list of worksheets"
issue again (e.g., your students who couldn't login, etc.) let me
know!
----------------------------------
Technical stuff for the record. All I did is a hack that probably
does not address the root cause. Here's what I did (this patch is
not posted anywhere -- I'm curious what Mike and Rado think -- I
pointed out this exact issue with setting the name attribute on the
worksheets to them before).
sagenb@mod:~/sage_install/sage-4.7/devel/rkirov-flask$ hg diff
diff --git a/sagenb/notebook/worksheet.py b/sagenb/notebook/worksheet.py
--- a/sagenb/notebook/worksheet.py
+++ b/sagenb/notebook/worksheet.py
@@ -720,10 +720,14 @@
sage: W.name()
u'A renamed worksheet'
"""
- if len(name.strip()) == 0:
- name = lazy_gettext('Untitled')
- name = unicode_str(name)
- self.__name = name
+ try:
+ if len(name.strip()) == 0:
+ name = lazy_gettext('Untitled')
+ else:
+ name = unicode_str(name)
+ self.__name = name
+ except RuntimeError:
+ self.__name = lazy_gettext('Untitled')
def set_filename_without_owner(self, nm):
r"""
A few minutes ago I found that when I created new worksheets on
nt.sagenb.org, I couldn't view them (same weird infinite recursion
type bug). I restarted the server, and suddenly I could view them.
Also, sagenb.org gave a "server is too busy" error, which I guess
comes from twisted. I restarted it too.
So there is something wrong at present with the sagenb.org installs.
I'll start when I get time with looking into Mike's patch.
Hi,
I reverted the patch that I had made, and instead rebased and applied
Mike Hansen's patch (that Rado kindly dug up). *After* doing this I
could view the worksheet you mention above (as the admin user).
Before doing that I couldn't.
So, please, please try things out and let me know whether or not the
problem is fixed.
Hi,
I fixed another bug uncovered by your worksheets (thanks). Can you
try again, and report?
William
I found yet another issue by randomly looking through worksheets, and
fixed that one as well.
I'm restarting the servers now (which should take about 2 minutes).
William