[BUG] Multimodal fields not persisted when creating new models via API #13
Labels
No labels
blocked:lint-failed
blocked:needs-decision
blocked:no-changes
blocked:no-procedure
blocked:preflight
blocked:verify-failed
bug
feature-request
in-progress
lint-cleanup
ops-task
quickfix
security/high
security/medium
test-coverage
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/vllm_mm#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
When creating a new model via
POST /api/models, theModelRepository.create()method inbackend/app/repositories/model_repository.pydoes not pass themultimodal,mmproj_path, andmmproj_sha256fields from the creation payload to the databaseModelRecord. These fields are silently dropped.Affected File
backend/app/repositories/model_repository.pyline 78-92Root Cause
The
ModelRecordconstructor call omits the multimodal fields:Impact
Models created as multimodal (vision) models via the API or frontend will not have their multimodal flag or projector file paths saved. When the model is later started, the
mmprojargument will not be passed to llama.cpp, causing vision inference to fail.Expected
Add the missing fields: