From 1a849908c32fcff49548f4fc61eb0124d42abc2f Mon Sep 17 00:00:00 2001 From: lane Date: Thu, 12 Nov 2026 15:51:29 -0400 Subject: [PATCH] Bump Lemonade: 1bit-MONSTER/lemonade 74e6b2501301 Gitlink only, as the automation writes it (no registry entry exists for Lemonade, so the gitlink is the single pin record). Moves ad89e8b76d89 -> 74e6b2501301, which is the fork's main and carries the two fixes that validating the previous pin found: 74e6b2501 onebit: declare the classification mode, and compare the memory fit in one unit (#52) Why that matters rather than being a routine step: the pinned tree at ad89e8b76 **failed two of its own tests**, and nothing else would have said so -- BackendModeContractTest FAIL onebit: 'classification' implemented and not declared agree MachineFitTest 2 hardware filter test(s) failed -> 141/143 `OnebitServer` derives from `LlamaCppServer`, which implements `IClassificationServer`, so the descriptor's capability is stamped whether or not `supported_modes` names it; and the memory-fit fixture carried `JustOver = 26.0` decimal GB against a 25.6 **GiB** threshold, which only passed while the two units were compared without converting -- the unit bug fork #44 (engine#1381) fixed. Measured on the pinned tree with a from-scratch configure and a full build (206 test binaries): before 141/143 (the two above) after 143/143, 0 failed gen_backend_boilerplate.py --check rc 0 (the README union the port spliced is regenerated) --- third_party/lemonade | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/third_party/lemonade b/third_party/lemonade index ad89e8b7..74e6b250 160000 --- a/third_party/lemonade +++ b/third_party/lemonade @@ -1 +1 @@ -Subproject commit ad89e8b76d899db324996ac4e6ac63aafa1442d7 +Subproject commit 74e6b2501301c3a5e762cee5f14213d92d292fa8