-
Notifications
You must be signed in to change notification settings - Fork 8
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
- Run cell A which takes a long time to compute.
- Cell B relies on cell A, so it will queue up to run.
- Modify cell B (e.g., forgot to change something), it becomes marked as stale.
- Run cell B with
ctrl+enterso that it will queue up to run (even if it runs once with the original code, I would still want it to queue to run again with the new code). - When cell A finishes running and cell B runs, it will still be marked stale because it won't have run the new code.
Environment
Details
(Oh hey, this was still in my clipboard from the last one.)
marimo VS Code Extension Diagnostics
=====================================
Language Server (LSP):
UV Bin: Discovered (C:\Users\andrew\.local\bin\uv.exe)
UV: uv 0.9.26 (ee4f00362 2026-01-15) ✓
Using bundled marimo-lsp via uvx
Python Extension:
Interpreter: c:\Users\andrew\Code\project\code\.venv\Scripts\python.exe
Version: 3.13.9.final.0
Environment: VirtualEnvironment (biaxtic)
Python Language Server (ty):
Status: running ✓
Version: 0.0.12 (4b74e4ded 2026-01-14)
Python: c:\Users\andrew\Code\project\code\.venv\Scripts\python.exe (3.13.9.final.0)
Ruff Language Server:
Status: running ✓
Version: 0.11.13
Extension Configuration:
Version: 0.9.2
UV integration disabled: false
System Information:
Host: desktop
IDE: Visual Studio Code
IDE version: 1.108.1
Platform: win32
Architecture: x64
Node version: v22.21.1
Common Issues:
1. If notebooks won't open:
- Check Python interpreter is selected
- Ensure marimo and pyzmq are installed
- Check 'marimo-lsp' output channel for errors
2. If features are missing:
- Ensure marimo version is >= 0.19.0
- Try reloading the window
Steps to reproduce
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working