[Bug]: MiniMax stale-roster refresh has no destination guard for Custom base URLs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
Research direction
Read src/providers/stale-model-roster-migration.ts around line 104 and compare the MiniMax entries with the guarded Meta, DeepSeek, and Alibaba International entries. Check how destinationBaseUrls is used to restrict roster refreshes, then confirm the refresh applies only to official MiniMax base URLs and preserves custom gateway rows.
Written by the indexing model from the issue text.
Description
Client or integration
Other
Area
Catalog / models
Summary
The startup stale-roster refresh for minimax and minimax-cn (src/providers/stale-model-roster-migration.ts:104) sets no destinationBaseUrls, unlike the Meta, DeepSeek and Alibaba International entries in the same table. A saved MiniMax row whose base URL points at another gateway can therefore have its model roster rewritten to the official MiniMax list, even though only the official MiniMax endpoint publishes that roster. Expected: the refresh applies only to rows whose destination is an official MiniMax base URL, as the other guarded entries do.
Reproduction
- Save a
minimaxprovider row with a Custom base URL (any OpenAI-compatible gateway) and a model list from before MiniMax-M3.1. - Start opencodex 2.93.0.
- Observe that the saved model list is replaced by the official MiniMax roster.
Version
2.93.0
Operating system
Any
Provider and model
No response
Logs or error output
n/a
Screenshots and supporting files
No response
Redacted configuration
n/a
Checks
- I searched existing issues and documentation.
- I removed secrets, tokens, account details, request credentials, and personal data.
- Dominant language
- TypeScript
- Stars
- 16.9k
- Forks
- 1.3k
- Avg merge
- 15h 24m
- Merged PRs (30d)
- 678
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lidge-jun/opencodex
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
lidge-jun/opencodex#7728 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement streaming
Difficulty 5/5 Over a week Newbie friendliness 12/100
lidge-jun/opencodex#7905 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
account-pool bug
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Maintainers usually reply within 1 day
-
account-pool bug provider
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
All issues in lidge-jun/opencodex
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
b310-digital/teammapper#1515 ·
Maintainers usually reply within 1 day
-
onenote
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
obsidianmd/obsidian-importer#689 ·
-
In a half-screen window, the title bar cuts the workspace and version names until they can't be readOpenbug launch local use macOS Windows
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[Integration]: eRPCOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ava-labs/builders-hub#4826 ·
Maintainers usually reply within 1 day
-
记忆分析的默认模型显示与实际使用不一致Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day