ISSUE DESCRIPTION jarvis agents list Traceback Description Learning OpenJarvis on a…
- User
ISSUE DESCRIPTION
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 tagADDITIONAL ADVICE
Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use
git checkout <file>to restore the file to its original state. You can also reset all changes in the repository usinggit reset --hardcommand. Additionally, you can usegit stashandgit stash popto temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you callsubmit) usinggit statusorgit diffcommands. However you don't need to usegit addorgit commitbefore submitting your changes. In fact,submitonly submits currently unstaged changes because it usesgit diffto get the changes that need to be submitted.CHECKLIST
Before submitting your solution, please go over the following checklist and make sure you've done everything:
- If an error was reported in the issue description, I have successfully reproduced it.
- If an error was reported in the issue description, I have confirmed that my fix resolves the error.
- I have thought about edge cases and made sure my fix handles them as well.
- I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.
Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!
(Current directory: /OpenJarvis, current file: none) bash-$
- Assistant
I’ll inspect the agent CLI and its tests, then reproduce both the Rich markup failure and the underlying exception that it masks. I’ll aim to fix error rendering safely and, if possible, address the root cause rather than merely exposing it.
- Assistant
The traceback confirms a general bug: exception text is interpolated into Rich markup, so any bracketed content (common in connection errors such as
[Errno 111]) corrupts the error handler itself. I’ll now inspect all command handlers and the manager’s listing path to determine why an idle Ollama process could affect a database-only operation. - Assistant
agents listitself only performs SQLite reads, so Ollama unloading should not matter. A likely cause is persisted agent status data containing Rich-sensitive brackets, or a transient SQLite error whose text includes[Errno ...]; either way, dynamic table values and exception messages must not be parsed as markup. I’ll inspect schema conversion/recovery and reproduce the exact markup crash with a mocked exception before changing code. - Assistant
The source reveals a second concrete rendering defect: unknown/transitional status values produce
[]status[/], which raises a RichMarkupError; the catch block then embeds that markup-containing exception text and raises the reported[/red]mismatch. I’ll fix both layers by representing table data as literalTextobjects and printing exceptions with markup disabled. I’ll apply the safe error path consistently within this command module so the same masking failure cannot occur in sibling agent subcommands. - Assistant
The direct reproduction now prints the original bracket-heavy exception without a traceback. Next I’ll add no repository tests (per instruction), but use a temporary in-process CLI harness to exercise
agents listwith (1) an unknown status and bracketed fields and (2) a mocked[Errno]failure. Then I’ll run the existing agent CLI tests and lint/type checks used by the project. - Assistant
The temporary harness verifies both edge cases and the focused suite passes (52 tests). The reported
[/red] at position 65strongly matches the cascading-error pattern from an invalid empty status tag; I’ll confirm Rich’s exact message, run Ruff, and review the diff for scope and accidental lockfile changes before final submission. - Assistant
Rich reproduces the same cascade at essentially the reported character offset, confirming the root cause. Ruff is declared only as a development dependency and is not installed in the current environment; I’ll restore the unrelated pre-existing/generated lockfile drift, then run Ruff ephemerally with a frozen project lock so verification does not alter repository metadata.
- Assistant
Lint passes, while the formatter requests a mechanical layout change. I’ll apply it, inspect exactly what changed, and rerun the focused tests after formatting.
- Assistant
The focused suite still passes. The formatter also changed two unrelated pre-existing sections due to a tool-version formatting difference, so I’ll restore those hunks to keep the patch narrowly scoped. I’ll also verify the set of statuses written by runtime code; this determines whether the empty-style path can naturally occur after an ask operation.
- Assistant
Runtime status writes are all covered by the style map, so the reported agent likely hit some other transient exception; importantly, the safe error helper now preserves that original diagnostic instead of crashing while rendering it. The table fix remains worthwhile defensive handling for legacy/corrupt/custom statuses and bracket-containing persisted fields. I’ll perform one final end-to-end invocation against a temporary real SQLite manager with the reported idle/deep-research row, rerun the exact markup-error reproduction through the command, and then review the checklist before submission.
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
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
Qwen/Qwen3.6-27BCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare side by side →
- xiaomi/mimo-v2.5-proCompare 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 →