Skip to content

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

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

Open
eust-w opened this issue Apr 24, 2025 · 0 comments · May be fixed by #533
Open

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

eust-w opened this issue Apr 24, 2025 · 0 comments · May be fixed by #533
Labels
Bug Something isn't working UI TARS

Comments

@eust-w
Copy link

eust-w commented Apr 24, 2025

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

@eust-w eust-w added Bug Something isn't working UI TARS labels Apr 24, 2025
eust-w pushed a commit to eust-w/UI-TARS-desktop that referenced this issue Apr 24, 2025
eust-w pushed a commit to eust-w/UI-TARS-desktop that referenced this issue Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working UI TARS
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant