Restart Jupyter kernel if package is installed via bash too #3178
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the problem that this fixes or functionality that this introduces? Does it fix any open issues?
This PR introduces functionality to restart the Jupyter kernel if a package is installed via bash commands. It addresses issues with kernel state management that arise when new packages are installed via bash, ensuring that changes are correctly reflected without manual intervention.
Give a summary of what the PR does, explaining any non-trivial design decisions
This PR refactors the
ServerRuntime
class to handle kernel restarts more effectively. Key changes include:restart_kernel
method to restart the Jupyter kernel and ensure that it is re-initialized with necessary code.parse_pip_output
method to handle package installation messages and determine if a kernel restart is needed based on the output ofpip install
commands.kernel_init_code
torestart_kernel
method and removed unusedkernel_init_code
attributes from action parser classes (CodeActActionParserIPythonRunCell
andCodeActSWEActionParserIPythonRunCell
).These changes ensure that kernel restarts and re-initializations are handled automatically, improving the reliability of the development environment.
Other references
Event history of ollama/llama3