Skip to content

[Bug]: Overly Strict Validation for VLM Key Fields During Preset Import #532

@eust-w

Description

@eust-w

Version

0.1.0

Model

UI-TARS-7B-DPO

Deployment Method

Cloud

Issue Description

When importing a preset configuration file, the system requires three VLM key fields (vlmBaseUrl, vlmApiKey, and vlmModelName) to be present in the configuration file, even if these fields have already been set in the Settings-VLM settings page.

Expected behavior: The system should work as long as VLM key fields are provided either in the Settings-VLM settings page or in the imported configuration file. When importing a configuration with some fields missing, it should use the existing values from the settings page.
Actual behavior: Import fails with validation errors if any of the VLM key fields are missing in the configuration file:
CopyInsert
Error invoking remote method 'setting:importPresetFromText': [
{ "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "vlmBaseUrl" ], "message": "Required" },
{ "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "vlmApiKey" ], "message": "Required" },
{ "code": "invalid_type", "expected": "string", "received": "undefined", "path": [ "vlmModelName" ], "message": "Required" }
]

Image

Error Logs

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugSomething isn't workingUI TARS

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions