Repository navigation
chore: SKaiNET 0.62.1 / transformers 0.63.0 for all samples - #47
Merged
Merged
Conversation
…otlin 2.4.21 Pins and catalog comments only. Kotlin follows the engine to 2.4.21: the SIMD128 sidecar the web verifier runs on needs a Kotlin/Wasm linker at least as new as the engine's. The README names the transformers version the verifier ships with.
Pins and the catalog comment only; the sample keeps Kotlin 2.4.10.
Pins only. GGUFTokenizer and the legacy LlamaRuntime constructor stay deprecated in transformers 0.63.0 and are still used by the JVM playground (follow-up).
IrisDemo, MnistJavaDemo, TinyTransformer, SinusApproximator, GloVeEmbeddings, TDALab and MNISTDemo move from 0.61.0 to 0.62.1: pins, catalog and settings comments and the MnistJavaDemo README line. No source changes; Kotlin stays 2.4.10 (the 0.62.1 klibs are built with 2.4.21 and load on JVM and wasm).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves every sample except LayaMoE (already there) to engine SKaiNET 0.62.1; the three samples that use SKaiNET-transformers (SemanticEmojiFilter, KernelRace, KllamaDemo) go to 0.63.0 at the same time. One commit per transformers sample, one for the seven engine-only samples. Pins, catalog and settings comments and two README version mentions only; no source changes.
Engine 0.62.x is the JVM / Kotlin-Wasm parity release (every kernel on the wasm tier, fused SIMD128 and FFM kernels, browser IO parity); 0.62.1 fixes the native packed-kernel bindings (SKaiNET #1436) that the Q8_0 lane uses on the desktop JVM. Transformers 0.63.0 is additive (Laya expert heads and routing, used by LayaMoE only).
Kotlin: SemanticEmojiFilter moves from 2.4.20 to 2.4.21, the engine's own Kotlin, because its web verifier runs on the SIMD128 sidecar and an older Kotlin/Wasm linker fails on it. The other samples keep 2.4.10; the 0.62.1 klibs (built with 2.4.21) load on JVM and wasm as before, and the catalog comments say so.
Verified locally against Maven Central, one sample at a time:
:shared:jvmTest,:shared:testAndroidHostTest,:cli:compileKotlin,:androidApp:assembleDebug, the shared and composeApp wasm compiles; with-PlayaVerifier=true:verifier:jvmTest,:composeApp:compileKotlinJvm, the verifier and webVerifier wasm compiles).:composeApp:compileKotlinJvmand the webWorker production wasm compile.:shared:jvmTest,:composeApp:compileKotlinJvm, the shared and composeApp wasm compiles.GGUFTokenizerand the legacyLlamaRuntimeconstructor are still deprecated (not removed) in 0.63.0; the follow-up from chore(kllamademo): SKaiNET 0.60.0 / transformers 0.61.0 #41 stands.build.jvmTest, app desktop compile, library and app wasm compiles; MNISTDemo also:cli:test.Known and unchanged: MNISTDemo
:cli:testfails its two CNN accuracy tests (MnistAccuracyTest,ArrayIndexOutOfBoundsExceptionin weight loading). This is the pre-existingcreateMNISTCNN()bug noted in #39 (adense(10)afterflatten()with zero in-features); the same two tests fail identically on develop with the 0.61.0 pins, re-run today to confirm. Everything else in MNISTDemo is green.