-
Notifications
You must be signed in to change notification settings - Fork 0
feat: model hub visibility & features + review fixes v4 #27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
0f8c84a
b3ae575
8338b23
528eb8d
e14a543
78f922d
214c637
12753bd
bda8325
be67870
38e080c
dcccf7f
caef8f9
c34bd9e
03b96f5
a7a5588
d22047a
296b957
3466563
43b1987
07b035e
eafa0fc
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -90,6 +90,10 @@ spec: | |
| env: | ||
| - name: CONFIG_PATH | ||
| value: /config/router_dir/config.yaml | ||
| - name: LITELLM_CONFIG_PATH | ||
| value: /config/litellm_dir/config.yaml | ||
| - name: DATABASE_URL | ||
| value: postgresql://postgres:***@127.0.0.1:5432/postgres | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The |
||
| - name: DBUS_SESSION_BUS_ADDRESS | ||
| value: unix:path=/run/user/1000/bus | ||
| - name: LITELLM_MASTER_KEY | ||
|
|
@@ -127,6 +131,8 @@ spec: | |
| volumeMounts: | ||
| - mountPath: /config/router_dir | ||
| name: router-config | ||
| - mountPath: /config/litellm_dir | ||
| name: litellm-config | ||
| - mountPath: /app/data | ||
| name: dataset-data | ||
| - mountPath: /config/gemini_auth | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Align simple-tier context metadata with the router clamp.
This advertises
agent-simple-coreas ~256K context, butrouter/main.pyclampsagent-simple-coreusing a 32K minimum context. Clients relying on Model Hub metadata can submit prompts that the router/runtime path won’t actually honor. Pick one source of truth and update either this metadata or the router clamp.🤖 Prompt for AI Agents
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Be extra mindful of any flow/logic changes to the tiering and fallback chains, and consider full implications.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Length of output: 9692
@sheepdestroyer— confirmed the clamping logic is still active on this branch. Here's the full picture:What the code does (Lines 1804–1821 of
router/main.py)For
agent-simple-corewith a near-empty prompt this yields_safe_max ≈ 30 720.config.yamlmeanwhile advertisesmax_tokens: 256000.Full implications
Recommendation (minimal, safe)
The only change that avoids any flow impact is aligning the static metadata with the runtime floor already enforced by the router:
This does not change any routing decision, fallback chain, or LiteLLM router behavior — it only corrects what the Model Hub advertises to clients to match what the router actually enforces as its guaranteed minimum. The static entry is a cold-start safety net; once the roster sync runs, each dynamically registered deployment gets its own accurate per-model context from OpenRouter.