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

Sequential run not working (queued execution cancelled automatically) #5098

Open
pedrovgp opened this issue Dec 3, 2019 · 3 comments
Open

Comments

@pedrovgp
Copy link

pedrovgp commented Dec 3, 2019

If I run a bunch of cells in sequence, only the first runs. All others get a "finished" timestamp equal to the first cell's timestamp, but none was really executed. In the picture below, all cells were queued almost at the same time.
image

Another simple step-by-step example:

  1. I ran the first cell, then the second after the first finished executing.
    image
  2. I modified b to be equal 23, then ran both cells in a sequence. The second cell's execution was queued, because the first execution had not finished. At the end, I got this:
    image
  3. I checked to see if b was modified, even though the cell did not show any output. But it was not:
    image
@Mateil04
Copy link

Same issue here. Any solution so far? Thanks!

@pedrovgp
Copy link
Author

Not really, I ended up going back to databricks, this is kind of a deal breaker.

@jasongrout
Copy link
Member

Does your server log show any errors? Do you see any errors in the javascript console in the web browser?

If not, can you reproduce the issue in a new, clean environment with a fresh installation of just the notebook?

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

No branches or pull requests

3 participants