You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browse filesBrowse the repository at this point in the historyBrowse files
Han Wang
committed
fix: three canonical-bridging P1s from review round 2
1. Sugar expansion keeps trainer-owned top-level `lora` at the
composition level instead of forwarding it to the learned child
(which the pt bridge builder rejects), restoring the concise
dpa4+bridging_method+lora form. The key routing is now a four-way
table (composition / consumed / trainer / learned-child) whose
coverage of the standard+dpa4 argcheck schemas is pinned by
test_routing_covers_the_argcheck_schema: a new argcheck model key
fails the test until it gets an explicit routing decision, instead
of silently landing on the child. The guard immediately surfaced
use_compile and enable_tf32 as previously-undecided keys (both
routed to the learned child, preserving behavior).
2. pt LinearEnergyModel.update_sel: the shared-config reconstruction
loop now skips the `inner_potential` child too. Normalization
always inserts `shared_dict: {}`, so the default CLI path entered
the reconstruction loop and dereferenced the analytical child's
missing descriptor (KeyError). New test runs on a NORMALIZED config.
3. The shared dpmodel/pt_expt linear builder rejects bridged
compositions with a third child (e.g. pairtab): no common execution
route exists (pairtab is dense-only, the bridged pair graph-only),
matching the pt builder's exact-two-child constraint and message.
0 commit comments