I was about to post a possible notebook bug but perhaps the new
version of sagenb will have fixed it anyway (if it is a bug).
I run a server (on a ubuntu linux machine), with the server running
under user "sage" and with a server-pool containing users sage0,
sage1, sage2, sage3. All works fine (e.g. I see that worksheet
processes use several of these users at once).
The machine has magma installed. If I put in a cell:
%magma
2+2;
then I get an error message saying
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "_sage_input_6.py", line 4, in <module>
print _support_.syseval(magma,
ur\u0027\u0027\u00272+2;\u0027\u0027\u0027,
\u0027/home/sage/.sage/sage_notebook.sagenb/home/cremona/1/cells/9\u0027)
File "", line 1, in <module>
File
"/usr/local/sage/sage-4.3.2/local/lib/python2.6/site-packages/sagenb-0.6-py2.6.egg/sagenb/misc/support.py",
line 469, in syseval
system.chdir(dir)
File
"/usr/local/sage/sage-4.3.2/local/lib/python2.6/site-packages/sage/interfaces/magma.py",
line 905, in chdir
magma.eval('ChangeDirectory("%s")'%dir)
File
"/usr/local/sage/sage-4.3.2/local/lib/python2.6/site-packages/sage/interfaces/magma.py",
line 520, in eval
raise RuntimeError, "Error evaluating Magma code.\nIN:%s\nOUT:%s"%(x, ans)
RuntimeError: Error evaluating Magma code.
IN:ChangeDirectory("/home/sage/.sage/sage_notebook.sagenb/home/cremona/1/cells/9");
OUT:
>> ChangeDirectory("/home/sage/.sage/sage_notebook.sagenb/home/cremona/1/cells
^
Runtime error in 'ChangeDirectory': Cannot change directory to
"/home/sage/.sage/sage_notebook.sagenb/home/cremona/1/cells/9"
(Permission denied)
When I look in /home/sage/.sage/sage_notebook.sagenb/home/cremona/1/cells/9
I see
s...@selmer:~/.sage/sage_notebook.sagenb/home/cremona/1/cells/9$ ls -al
total 8
drwx------ 2 sage sage 4096 2010-02-06 16:37 .
drwxr-xr-x 11 sage sage 4096 2010-02-06 16:37 ..
-- so the whole directory tree above this has 755 permissions, while
this directory only has 700, and this might explain why the worksheet
process (which I think is running under sage0) has a problem. But if
that is the case, why does everything else work (e.g. 2+2; without the
%magma)?
John
On 6 February 2010 16:35, William Stein <wst...@gmail.com> wrote:
> On Sat, Feb 6, 2010 at 5:12 AM, Pat LeSmithe <qed...@gmail.com> wrote:
>> On 02/06/2010 04:01 AM, Minh Nguyen wrote:
>>> Merged in sagenb:
>>
>> Just a quick note: These tickets are part of SageNB 0.7.4, but Sage
>> 4.3.2 contains version 0.6.
>
> Hi,
>
> I'm surprised sagenb-0.7.4 isn't in 4.3.2. Actually, I'm surprised
> 4.3.2 was just released, since to me getting the updated sagenb in,
> plus fixing the segfault on OS X (#8177) was very important (I was
> going to do that after Minh handed off the last rc to me).
>
> I'm not going to make binaries for 4.3.2, since deploying such an old
> notebook version in new versions of Sage is nuts. So I'll work on a
> quick 4.3.3, which:
>
> (1) includes a fix for that critical OS X issue (if it isn't in
> 4.3.2 already),
> (2) and the new sagenb release, and
> (3) I will test that upgrading from 4.3 and 4.3.1 to 4.3.3
> actually works (we had a ton of problems with upgrading from 4.3 to
> 4.3.1 not working).
>
> And this is what will actually get released and get binaries.
>
> Is there anything else that is critical that was missed/broken by
> 4.3.2 that I'm missing?
>
> -- William
>
> --
> To post to this group, send an email to sage-devel@googlegroups.com
> To unsubscribe from this group, send an email to
> sage-devel+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
>
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
