Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Ground truth: add Kotlin/Native target(s) to skainet-test-groundtruth (jvm/android only today)

Abierto
  • ¿Algo no está bien?
#1,301 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
kotlin
Área
testing

Línea de trabajo

Start with skainet-test/skainet-test-groundtruth/build.gradle.kts and inspect its kotlin { } targets and the commonMain dependencies, especially whether skainet-io-gguf supports Kotlin/Native. Check whether fixture generation needs changes or only Kotlin consumption. Done when a Kotlin/Native-only module can depend on the ground-truth validator and its fixtures; macosArm64() is the suggested first target.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement platform skill:native sub-issue

Problem

skainet-test-groundtruth's kotlin { } block only declares android() and jvm() targets (skainet-test/skainet-test-groundtruth/build.gradle.kts). There's no macosArm64() / iosArm64() / linuxX64() / any Kotlin/Native target at all.

That makes GroundTruthValidator(ops, factory) unusable from any Kotlin/Native-only consumer — for example an out-of-tree GPU backend that only publishes K/N targets (macOS/iOS) and has no JVM target to fall back to. Right now the only way to get any ground-truth coverage for a backend like that is to hand-roll independent fixtures outside the module entirely, which duplicates exactly the hand-written-mapping problem #985/#986/#988 are already trying to avoid on the JVM/Python side.

Ask

Add at least one Kotlin/Native target (macosArm64 would cover the common Apple-Silicon dev case) to skainet-test-groundtruth, so GroundTruthValidator and its fixtures can be consumed by K/N-only modules the same way the skainet-backend-cpu src/goldenTest pattern already works on the JVM side.

Things worth checking first:

  • Does GGUF fixture loading (skainet-io-gguf) already build for K/N targets?
  • Does anything in commonMain currently reach for a jvm()-only API?
  • Does the Docker/PyTorch fixture-generation step need to change, or only the Kotlin consumption side?

Context

Ran into this concretely while trying to wire ground-truth validation into an out-of-tree, Kotlin/Native-only MLX/Metal backend module — ended up redefining that task around a small hand-written independent NumPy fixture instead, since the module couldn't be depended on at all from a K/N-only target set.

Related: #984, #985, #988.

Lenguaje dominante
Kotlin
Estrellas
52
Forks
15
Merge medio
1 d 8 h
PR fusionados (30 d)
37

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de SKaiNET-developers/SKaiNET

Todos los issues de SKaiNET-developers/SKaiNET

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.