Zum Hauptinhalt springen
Sichere ProgrammierungESP32-S3 vs ESP32-C3: cuál elegir según el papel del dispositivo(04.10.2026 um 12:55 Uhr)
•
Sichere ProgrammierungI built my brother a bedtime storyteller that runs on his laptop(04.10.2026 um 12:55 Uhr)
•
Sichere Programmierungstudy buddy(04.10.2026 um 12:55 Uhr)
•
Sichere ProgrammierungThe kiln bonus(04.10.2026 um 12:57 Uhr)
•
Sichere ProgrammierungLaravel Upgrade Checklist: How to Move an Old App Safely(04.10.2026 um 12:59 Uhr)
••
Sichere Programmierunginput type="url" rejects the URL before your normalizer ever runs(04.10.2026 um 13:00 Uhr)
••
Sichere ProgrammierungWebsites Are Learning to Gaslight Bots, and Honestly, Good(04.10.2026 um 13:00 Uhr)
•
AI & KI NachrichtenBest AI Tools for Students in 2026 (7 Picks, Mostly Free)(04.10.2026 um 13:00 Uhr)
•
Sichere ProgrammierungESP32-S3 vs ESP32-C3: cuál elegir según el papel del dispositivo(04.10.2026 um 12:55 Uhr)
•
Sichere ProgrammierungI built my brother a bedtime storyteller that runs on his laptop(04.10.2026 um 12:55 Uhr)
•
Sichere Programmierungstudy buddy(04.10.2026 um 12:55 Uhr)
•
Sichere ProgrammierungThe kiln bonus(04.10.2026 um 12:57 Uhr)
•
Sichere ProgrammierungLaravel Upgrade Checklist: How to Move an Old App Safely(04.10.2026 um 12:59 Uhr)
••
Sichere Programmierunginput type="url" rejects the URL before your normalizer ever runs(04.10.2026 um 13:00 Uhr)
••
Sichere ProgrammierungWebsites Are Learning to Gaslight Bots, and Honestly, Good(04.10.2026 um 13:00 Uhr)
•
AI & KI NachrichtenBest AI Tools for Students in 2026 (7 Picks, Mostly Free)(04.10.2026 um 13:00 Uhr)
•
Intelligence View
⚡ tsecurity.de Intelligence

GitHub Release: ollama/ollama v0.34.2-rc1 (16.09.2026)

Release v0.34.2-rc1 von ollama/ollama auf GitHub: model is one package with three jobs: the contract between the runner and the architectures, the opened…

Beitrag
0
Seite
0
↗ Quelle (GitHub · ollama/ollama)
Social ReaktionenReagiere als Erste:r — dein Feedback zählt!
ollama/ollamav0.34.2-rc116.09.2026@jessegross

model is one package with three jobs: the contract between the runner

and the architectures, the opened checkpoint, and building nn layers

from checkpoint tensors. Its files did not say which was which. base.go

carried the folded package's name over the interfaces and the registry,

root.go held the safetensors header scan next to Root, and quant.go

mixed the nvfp4 global-scale helpers with quant parameter resolution.


base.go becomes model.go, named for what it holds. root.go keeps Root

and Open; TensorQuantInfo and the header scan join quant.go, so

everything the checkpoint says about quantization is read and resolved

in one file. The global-scale helpers move to globalscale.go with their

tests. Root.Close, a no-op with one caller, goes. No code changes

otherwise.

Zum Aktualisieren ziehen
Nächster Beitrag