fix: declare orjson as a direct dependency#116
Merged
Conversation
litellm's request path imports orjson at runtime, but litellm only declares it under its 'proxy' extra, which raven does not install. orjson was therefore absent from the dependency graph (not in pyproject or uv.lock), so a fresh install lacked it and every real turn failed with 'APIConnectionError: OpenrouterException - No module named orjson', surfaced in the tui as the generic 'turn_failed (code=-32099)'. Declare orjson as a direct runtime dependency, mirroring litellm's own constraint (>=3.11.6,<4.0). Verified: a turn that previously failed now completes normally. Closes #113 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
arelchan
force-pushed
the
fix/declare_orjson_dependency
branch
from
July 13, 2026 09:21
7b676ac to
00e7610
Compare
10 tasks
0xKT
approved these changes
Jul 13, 2026
arelchan
pushed a commit
that referenced
this pull request
Jul 13, 2026
## Summary Bump project version 0.1.3 -> 0.1.4 to cut the next patch release. Ships the four fixes/features merged since v0.1.3: `raven upgrade` command (#112), onboard oauth browser login (#110), plugin dir on sys.path (#92), and orjson as a direct dependency (#116). Lockfile synced via `uv lock`. ## Type - [ ] Fix - [ ] Feature - [ ] Docs - [ ] CI / tooling - [ ] Refactor - [x] Other ## Verification - [x] Relevant lint / type checks pass locally ``` python3 scripts/check_commit_messages.py origin/main..HEAD # pass uv lock # raven 0.1.3 -> 0.1.4 ``` ## Risk - [x] Backward compatibility considered Version-only bump; no runtime code changed. The release tag (v0.1.4) is pushed after this merges. ## Related Issues N/A Co-authored-by: Claude (claude-opus-4-8) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Change description
Fixes a fresh-install crash where every real turn fails with
APIConnectionError: OpenrouterException - No module named 'orjson'(shown in the TUI as the generic
turn_failed (code=-32099)).Root cause: litellm's request path imports
orjsonat runtime, but litellmonly declares it under its
proxyextra, which raven does not install. Soorjsonwas absent from raven's dependency graph entirely (not inpyproject.toml, not inuv.lock). Any install (git clone && uv sync, orthe release wheel) therefore lacked it, and the first message a user sends
crashes the turn.
Fix: declare
orjsonas a direct runtime dependency so every installresolves it.
Verified locally: a turn that previously failed with the missing-orjson
error now completes normally after the dependency is declared.
Type of change
Related issues
Closes #113
Checklists
Development
Security
Code review