fix: recover eligible model GPU routes
This commit is contained in:
17
README.md
17
README.md
@@ -451,11 +451,24 @@ routes per model, preserving successful-route and queue ordering without
|
||||
discarding capacity on lower-ranked GPUs when the preferred tranche cannot run
|
||||
the model.
|
||||
|
||||
Version `2026.09.20.1` corrects the community verification precheck: an exact
|
||||
model/GPU route marked `未验证` with no records is eligible, while `已验证`, `验证中`,
|
||||
and unknown states stay blocked. A `验证失败` route may use a different framework
|
||||
only when every previous record explicitly failed and names its framework; the
|
||||
fresh check before submission rejects any framework that has already failed on
|
||||
that GPU. The official framework evidence and deterministic preflight gates
|
||||
still apply. When recent-update discovery is exhausted, a bounded 500-model
|
||||
download-ranked ModelScope scan checks a rotating 200-row window of older
|
||||
popular models without exceeding the platform's 3,000-row pagination ceiling.
|
||||
Architecture history backfill now
|
||||
sends the date format accepted by ModelHub. The full-repository-size OOM rule is
|
||||
unchanged because ModelHub's own preflight uses that size.
|
||||
|
||||
## Deploy
|
||||
|
||||
Create a tag and submit the repository URL plus tag in "我的适配智能体".
|
||||
|
||||
```bash
|
||||
git tag -a agent-v34 -m "ModelHub agent 2026.09.18.1"
|
||||
git push origin main agent-v34
|
||||
git tag -a agent-v35 -m "ModelHub agent 2026.09.20.1"
|
||||
git push origin main agent-v35
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user