Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simple Server API - wrong cell results #9785

Closed
sagetrac-dpoetzsch mannequin opened this issue Aug 23, 2010 · 6 comments
Closed

Simple Server API - wrong cell results #9785

sagetrac-dpoetzsch mannequin opened this issue Aug 23, 2010 · 6 comments

Comments

@sagetrac-dpoetzsch
Copy link
Mannequin

sagetrac-dpoetzsch mannequin commented Aug 23, 2010

Using the Simple Server API I tried the following (after logging in of course):

At first I sent the code "sleep(10);5" to the server using the following URL:
http://localhost:port/simple/compute?session=theID&code=sleep(10)%3B5

Then, immediatly afterwards (this means command one was still computing) I sent the code "4+5" to the server using the URL
http://localhost:port/simple/compute?session=theID&code=4%2B5

Then, after 10 seconds, I looked at the results of both commands using
http://localhost:port/simple/status?session=theID&cell=2
and
http://localhost:port/simple/status?session=theID&cell=3

Both cells had 5 as result, which should be only the result of the first
cell.

CC: @jasongrout

Component: notebook

Reviewer: Karl-Dieter Crisman

Issue created by migration from https://trac.sagemath.org/ticket/9785

@sagetrac-mmanashirov
Copy link
Mannequin

sagetrac-mmanashirov mannequin commented Dec 24, 2011

Attachment: trac_9785_fix_wrong_cell.patch.gz

This fixes the problem for me.

@kcrisman
Copy link
Member

comment:1

Sadly, the simple server does not work with the current notebook, and the Sage cell server has more or less superseded it.

@kcrisman
Copy link
Member

Reviewer: Karl-Dieter Crisman

@kcrisman
Copy link
Member

comment:2

Although we'll close this, I hope the code here will someday prove useful, though!

@kcrisman
Copy link
Member

comment:3

Note that #11409 would remove this completely.

@kcrisman
Copy link
Member

comment:4

This has now been removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants