Aias00 opened a new issue, #806:
URL: https://github.com/apache/rocketmq-dashboard/issues/806
### Before Creating the Bug Report
- [x] I have searched the existing issues and pull requests.
### Runtime platform environment
N/A
### RocketMQ version
rocketmq-studio branch
### JDK Version
N/A
### Describe the Bug
The legacy Settings page uses `qwen` as the provider value for Tongyi Qwen:
```tsx
{ value: 'qwen', label: '通义千问' }
```
However, the backend LLM config service and the newer LLM settings page use
`tongyi` as the provider key. `LlmConfigService.normalizeProvider()` only
accepts keys present in its provider map, so `qwen` is treated as an unknown
provider and normalized to `openai`.
This can silently save or load the wrong provider after selecting Tongyi
from the Settings page.
### Steps to Reproduce
1. Open the Settings page.
2. Select `通义千问` as the LLM provider.
3. Save or test the settings.
4. Observe that the frontend submits `qwen`, while the backend provider map
expects `tongyi`.
### What Did You Expect to See?
All Studio LLM settings surfaces should use the same provider key for Tongyi
Qwen. Existing `qwen` values should be normalized to `tongyi` for compatibility.
### What Did You See Instead?
The Settings page emits `qwen`, and the backend normalizer can fall back to
`openai`.
### Additional Context
This is in the AI Native / LLM configuration scope.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
