zeekay
b088668508
Continuous integration / Test Suite (ubuntu-latest) (push) Canceled after 0s
Continuous integration / Rustfmt (push) Successful in 46s
Continuous integration / Clippy (push) Successful in 3m28s
Continuous integration / Check (ubuntu-24.04) (push) Canceled after 0s
Continuous integration / Check (ubuntu-latest) (push) Canceled after 0s
Two [[bin]] targets in this workspace were both named hanzo-train, so both
uplifted to target/<profile>/hanzo-train and whichever linked last decided
what that path held:
hanzo-train/src/main.rs trains a DSpark draft through hanzo_nn::AdamW
and writes a checkpoint the engine's
qwen3_dspark loader reads.
hanzo-training/src/bin/train.rs
a config CLI whose `train` subcommand refuses,
because ModelWrapper carries no weights
(src/model.rs::unwired).
`cargo build --workspace` therefore left a trainer or a refusal at the same
path, nondeterministically. hanzo-training's binary is now named for its
crate; hanzo-train names the one thing that trains.
The two callers that named the ambiguous path follow the rename:
scripts/ultimate_setup.sh built --package hanzo-training and then looked for
target/release/hanzo-train, and scripts/train_native_ultra.py ran
`--bin hanzo-train -- --config <yaml>`, a flag only hanzo-training's CLI has.
(cherry picked from commit cbb55ff31c4368275ded3d5e4825bb8fdabb4279)