jarvis agents list Traceback Description Learning OpenJarvis on a Windows machine with…
- User
jarvis agents list Traceback
Description
Learning OpenJarvis on a Windows machine with WSL2. I was wondering what would happen on a clean reboot and listed the agents. This worked the first two times and listed the "... My Assistant │ deep_research ...". I even used the ID to ask it questions which worked (jarvis agents ask b0e6dece007b "How can I contribute to the OpenJarvis Project"). I had not loaded the model (Gemma 4 31b) into Ollama (this was direct from an open WSL Ubuntu window). My alias for jarvis is jarvis() { cd "@" }
My config is terse # OpenJarvis configuration # Hardware: 13th Gen Intel(R) Core(TM) i9-13900K (32 cores, 62.6 GB RAM) # GPU: NVIDIA GeForce RTX 4090 (24.0 GB VRAM) # Full reference config: jarvis init --full
[engine] default = "ollama"
[engine.ollama] # host = "http://localhost:11434" # set to remote URL if engine runs elsewhere
[intelligence] default_model = "gemma4:31b"
[agent] default_agent = "simple"
[tools] enabled = ["code_interpreter", "web_search", "file_read", "shell_exec"]
Steps to Reproduce
- Start an initial WSL Ubuntu shell
- run "jarvis"
- this will list the --help command
- run "jarvis agents list"
- this will list a table with one agent b0e6dece007b │ My Assistant │ deep_research │ idle │ 0 │ 0
- run "jarvis agents ask b0e6dece007b "How are you""
- this will respond after it loads and starts the model, GPU memory is utilized
- run "ps -aux|grep ollama" in another shell window
- this will output two processes:
- ollama 196 0.0 0.3 3405152 220636 ? Ssl 11:29 0:01 /usr/local/bin/ollama serve
- ollama 1078 66.2 6.9 195616136 4544716 ? Sl 12:39 5:25 /usr/local/bin/ollama runner --ollama-engine --model usr/share/ollama/.ollama/models/blobs/sha256-280af6832eca23cb322c4dcc65edfea98a21b8f8ab07dc7553bd6f7e6e7a3313 --port 42291
- run "jarvis agents ask b0e6dece007b "How can I contribute to the OpenJarvis Project""
- This will respond
- Wait a bit, until GPU memory frees
- run the "ps -aux|grep ollama" in another shell window and see only the one ollam process for the "serve"
- run "jarvis agents list"
- see Traceback
Expected Behavior
Expected the table listing with one idle agent: b0e6dece007b │ My Assistant │ deep_research │ idle │ 0 │ 0
Actual Behavior
Traceback
Operating System
Linux
Python Version
3.12
Hardware
NVIDIA GPU
Engine
Ollama
Logs / Traceback
Traceback (most recent call last): File "/home/gru/projects/OpenJarvis/.venv/bin/jarvis", line 10, in <module> sys.exit(main()) ^^^^^^ File "/home/gru/projects/OpenJarvis/src/openjarvis/cli/__init__.py", line 122, in main cli() File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/click/core.py", line 1485, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/click/core.py", line 1406, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/click/core.py", line 1873, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/click/core.py", line 1873, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/click/core.py", line 1269, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/click/core.py", line 824, in invoke return callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/src/openjarvis/cli/agent_cmd.py", line 91, in list_agents console.print(f"[red]Error: {exc}[/red]") File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/rich/console.py", line 1698, in print renderables = self._collect_renderables( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/rich/console.py", line 1558, in _collect_renderables self.render_str( File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/rich/console.py", line 1448, in render_str rich_text = render_markup( ^^^^^^^^^^^^^^ File "/home/gru/projects/OpenJarvis/.venv/lib/python3.12/site-packages/rich/markup.py", line 167, in render raise MarkupError( rich.errors.MarkupError: closing tag '[/red]' at position 65 doesn't match any open tagInterface
No new interfaces are introduced.
- Assistant
Let me verify empirically what kind of exception message reproduces exactly this error, and check the rich version behavior:
- Assistant
All files have the anchor. Now run the sweep:
- Assistant
No unescaped
{exc}sites remain and everything compiles. Check for name shadowing ofescape: - Assistant
The sweep script modified the file since my read — re-reading:
- Assistant
Two more table-content sites in
agent_cmd.py: - Assistant
Now let me find the existing test setup and write a regression test for the reported scenario:
- Assistant
Now add regression tests reproducing the reported failure mode:
- Assistant
Tests pass. Verify they actually catch the bug by running against the unfixed file:
- Assistant
Both regression tests fail without the fix and pass with it. Now run the wider test suite for all touched modules and the linter:
- Assistant
Fix the lint issues — auto-fix import order, then wrap the long lines:
- Assistant
Wrap those 10 long lines:
- Assistant
__init__.pyand_banner.pyweren't touched by me — let me check whether these format diffs are pre-existing or introduced: - Assistant
CI only enforces
ruff check— which passes. Now the final verification run: - Assistant
Same 14 failures on the clean tree — all pre-existing and unrelated. The stash pop conflicted on
uv.lock(regenerated byuv run); restoring: - Assistant
All changes restored. Final verification — regression tests plus an end-to-end simulation of the user's exact failure:
- Assistant
The user's scenario now prints the actual error instead of a
MarkupErrortraceback. Final diff review: - Assistant
Done. Summary of the fix:
Root cause
jarvis agents listhit a real underlying error (in the user's case, most likely a transient failure opening~/.openjarvis/agents.dbunder WSL2), but the error handler itself crashed while reporting it:console.print(f"[red]Error: {exc}[/red]")Rich parses the interpolated exception message as markup. A message containing a bracketed absolute path — e.g. sqlite's
unable to open database file [/home/gru/.openjarvis/agents.db]— is parsed as a closing tag ([/home...]starts with/), which prematurely closes[red]and makes the trailing[/red]raiseMarkupError: closing tag '[/red]' ... doesn't match any open tag. So the user got a traceback instead of the real error message. (I reproduced this exactly with the repo's rich version.)Changes
-
Repo-wide fix of the vulnerable pattern — all 80
console.print(f"...{exc}...")markup sites across 22 files (src/openjarvis/cli/*,src/openjarvis/evals/cli.py) now use{escape(str(exc))}, withfrom rich.markup import escapeadded where missing. Any of them could crash — or silently drop text — the same way. -
Hardened
agent_cmd.pydynamic content — Rich also parses markup insideTablecells and plain prints, so user/model-derived strings are now escaped: agent names inlist/create/info/run, task descriptions,summary_memory, channel configs, search query/results, template names/descriptions, tool-call args in the live trace, and the agent's response inask(model output routinely contains[markdown](links)). -
Regression tests (
tests/cli/test_agent_cmd.py::TestMarkupSafety) — one reproducing the bracketed-path error message, one for an agent name containing markup. Both verified to fail on the unfixed code and pass with the fix.
Verification
uvx ruff check src/ tests/(what CI runs): passestests/cli/: 405 passed; the 14 failures are pre-existing (verified identical on the clean tree — missing optional deps likepolars, doctor/telemetry issues in files untouched here)tests/evals/: 587 passed- End-to-end simulation of the user's scenario now prints
Error: unable to open database file [/home/gru/.openjarvis/agents.db]cleanly with exit code 0 instead of a traceback
Note for the reporter: the fix doesn't make the underlying DB error go away — it unmasks it. If it recurs, the printed message will now show what actually failed.
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.
Identical first prompt
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- composer-2.5Compare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- gpt-5.6-solCompare side by side →
- fable-5Compare side by side →