Few Lost Sheep...
Yes... more models !
Today:
https://huggingface.co/DavidAU/Qwen3-53B-A3B-2507-TOTAL-RECALL-v2-MASTER-CODER
New:
https://huggingface.co/DavidAU/Qwen2.5-Microsoft-NextCoder-Soar-Instruct-FUSED-CODER-Fast-11B
Older:
https://huggingface.co/DavidAU/Qwen3-Instruct-6B-Brainstorm20x-128k-ctx
https://huggingface.co/DavidAU/Qwen3-Instruct-F16-6B-Brainstorm20x-128k-ctx
https://huggingface.co/DavidAU/Qwen3-Shining-Lucy-CODER-2.4B-e32
https://huggingface.co/DavidAU/Qwen3-Shining-Lucy-CODER-2.4B-e32-mix2
https://huggingface.co/DavidAU/Mistral-Magistral-Devstral-Instruct-FUSED-CODER-Reasoning-36B
Thanks in advance!
- Qwen2.5-Microsoft-NextCoder-Soar-Instruct-FUSED-CODER-Fast-11B we already did
- Qwen3-Instruct-6B-Brainstorm20x-128k-ctx and Qwen3-Instruct-F16-6B-Brainstorm20x-128k-ctx failed with submitting with
no architectures entry (, or } expected while parsing object/hash, at character offset 608 (before ""rope_theta": 100000...") at /llmjob/share/bin/llmjob line 1639.
probably due to corruptedconfig.yaml
. - All others I queued sucessfully.
You can check the status under https://hf.tst.eu/status.html
Oh god, config.yaml is a thing now? We are doomed, I say!
@nicoboss
@mradermacher
My bad ; fixed the config.json file for each - should be good to go.
Sorry about that!
Thanks so much.
.. Yaml... that is so 2024 ish.
oh - one more just uploaded...
DavidAU/Qwen3-42B-A3B-2507-TOTAL-RECALL-v2-Medium-MASTER-CODER
Little late to the party.
Qwen2.5-Microsoft-NextCoder-Soar-Instruct-FUSED-CODER-Fast-11B
actually failed because of a lack oftokenizer.model
so while it already was queued it did not get processed sucessfully.Qwen3-Instruct-6B-Brainstorm20x-128k-ctx
andQwen3-Instruct-F16-6B-Brainstorm20x-128k-ctx
I now sucessfully queued.Qwen3-42B-A3B-2507-TOTAL-RECALL-v2-Medium-MASTER-CODER
is now queued as well.
Oh god, config.yaml is a thing now? We are doomed, I say!
Luckely I was mistaken and just missremembered the file type fo the config.json
as simular data is inside the README.md
metadata as YAML. Am I the only one that likes the simplicity of YAML? There now even is YAML Path
simular to JSONPath
and XPath
. In totaly YAML fashion the YAML Path Standard got defined by some random person and now is the de-facto standard everyone uses: https://github.com/wwkimball/yamlpath/wiki/Segments-of-a-YAML-Path
Thank you again.
RE: Soar ; odd - there is no tokenizer.model for this one, nor a lot of other ones (??).
Tried re-uploading json files - no new commits.
Will try re-upload of the safetensor files in am local time ; in case one of these glitched.
Am I the only one that likes the simplicity of YAML?
Must be - it's got one of the most complicated specs that exists on this planet, and still can't decide whether no is a string or a boolean. There is nothing simple when a format isn't even interoperable between different parsers, all spec-compliant...
There would objectively be a lot less grief in the world if YAML didn't exist.