When running a Jupyter notebook with a Julia kernel, I've noticed that the kernel continues to execute subsequent code cells even after encountering a failed code cell (i.e., a cell that throws an error). This behavior is different from what I experience when using a Python kernel in Jupyter, where the execution stops at the first failed code cell.
I'm not sure if this is a bug or an intended behavior, but I would like to have the option to stop execution at the first failed code cell, just like with a Python kernel.
Steps to reproduce:
Create a new Jupyter notebook with a Julia kernel.
Add three code cells with the following content:
First cell: x = 1
Second cell: y = x + "string" (This should throw an error)
Third cell: z = x + 1
Run all cells in the notebook.
Observe that the third cell is executed despite the error in the second cell.
Expected behavior:
The execution should stop at the second cell (the first failed code cell), and the third cell should not be executed.
Actual behavior:
The third cell is executed even though there's an error in the second cell.
Environment:
versioninfo()
Julia Version 1.8.5
Commit 17cfb8e65ea (2023-01-08 06:45 UTC)
Platform Info:
OS: Linux (x86_64-linux-gnu)
CPU: 8 × Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-13.0.1 (ORCJIT, skylake)
Threads: 1 on 8 virtual cores
IJulia version: 1.24.0
Jupyter notebook version: 6.5.2
Please let me know if there's a way to change this behavior or if this is a bug. Thanks!
When running a Jupyter notebook with a Julia kernel, I've noticed that the kernel continues to execute subsequent code cells even after encountering a failed code cell (i.e., a cell that throws an error). This behavior is different from what I experience when using a Python kernel in Jupyter, where the execution stops at the first failed code cell.
I'm not sure if this is a bug or an intended behavior, but I would like to have the option to stop execution at the first failed code cell, just like with a Python kernel.
Steps to reproduce:
Expected behavior:
The execution should stop at the second cell (the first failed code cell), and the third cell should not be executed.
Actual behavior:
The third cell is executed even though there's an error in the second cell.
Environment:
Please let me know if there's a way to change this behavior or if this is a bug. Thanks!