feat: compact durable logs and refine framework routing
This commit is contained in:
21
README.md
21
README.md
@@ -396,11 +396,28 @@ the aggregate checkpoint remains the authoritative recovery input even while an
|
||||
archive shard is awaiting upload. ModelHub Git traffic is excluded from proxy
|
||||
routing in the container to avoid deployment-specific Git failures.
|
||||
|
||||
Version `2026.09.04.1` makes durable state synchronization content-addressed:
|
||||
unchanged cycles do not create commits, and a failed network push retries the
|
||||
same commit/generation. The write-ahead batch size is now 100; resolved intent
|
||||
rows are compacted to 200 recent entries and moved to monthly gzip archive
|
||||
branches. Raw community samples and the official model/GPU capability cache are
|
||||
bounded, so restart no longer needs to restore and rewrite multi-megabyte
|
||||
disposable caches.
|
||||
|
||||
The submission loop now treats account-capacity saturation and framework
|
||||
prerequisite responses as deferred policy outcomes rather than model failures.
|
||||
When a model has an official non-`transformers` route, that immediately
|
||||
executable route is selected before the platform's prerequisite-gated
|
||||
`transformers` fallback; a recorded non-transformers failure unlocks normal
|
||||
success-based transformer selection. Missing framework/task/profile fields in history are
|
||||
recovered from the durable task ledger. The evidence and category breakdown are
|
||||
documented in `docs/failure-analysis-2026-09-04.md`.
|
||||
|
||||
## Deploy
|
||||
|
||||
Create a tag and submit the repository URL plus tag in "我的适配智能体".
|
||||
|
||||
```bash
|
||||
git tag -a agent-v29 -m "ModelHub agent 2026.08.22.1"
|
||||
git push origin main agent-v29
|
||||
git tag -a agent-v30 -m "ModelHub agent 2026.09.04.1"
|
||||
git push origin main agent-v30
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user