Skip to content

Self-hosted models: remote code and tokenizer from the pinned revision; release 0.7.3 - #35

Merged
flujo-app merged 1 commit into
mainfrom
selfhost-pin-code-revision
Nov 12, 2026
Merged

flujo-app merged 1 commit into
mainfrom
selfhost-pin-code-revision

Conversation

@flujo-app

Copy link
Copy Markdown
Owner

A model that needs its own code (trust_remote_code, Nemotron) loaded its code and tokenizer files from the Hub's default branch, not from the pinned revision of its weights. vLLM's log said so: transformers warned "A new version of the following files was downloaded ... To avoid downloading new versions of the code file, you can pin a revision" (seen on the Nemotron deploy of Nov 12).

Now vllm_command() adds --code-revision and --tokenizer-revision with the profile's own revision whenever trust_remote_code is on. Both flags exist in vLLM 0.32.0 (checked with the CPU flag helper: --code-revision, --tokenizer-revision, --revision all present). A profile without remote code (Qwen) is unchanged. Version 0.7.3.

Tests (Windows, Node 22.13): Python settings tests 12/12 (new: the three revision flags carry the pinned revision; Qwen has none); test/selfhost-modal.test.mjs and test/model-provider.test.mjs 19/19. Linux: this PR's GitHub job.

@flujo-app
flujo-app merged commit 8c45de0 into main Nov 12, 2026
2 checks passed
@flujo-app
flujo-app deleted the selfhost-pin-code-revision branch November 12, 2026 12:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant