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

[Lane 3 · ios] Precision/Recall/F1 — iOS target parity check

Abierto
  • ¿Algo no está bien?
#1,231 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
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Tranquilo
Stack tecnológico
ios, kotlin
Área
mobile-dev, testing-qa

Línea de trabajo

After #1229 is merged (or by checking out its branch), read the contributing guide’s “Build from source” section and run ./gradlew :skainet-backends:skainet-backend-cpu:iosSimulatorArm64Test --tests "sk.ainet.exec.metrics.*" on a Mac with Xcode. Compare results with the JVM run; if the simulator runtime is unavailable, try macosArm64Test and note which task you ran. Done means posting the target, toolchain versions, exact task, result, and any issues on #1222.

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

Descripción

coding good first issue platform size:xs skill:ios sub-issue

Sub-issue of #1222 (Precision, Recall and F1Score metrics).

Lane: 3 · Platform verification · iOS
Skill needed: Kotlin/Native Apple (Xcode command-line tools, an iOS simulator runtime) build tooling — running a Kotlin Multiplatform module's tests on this target. No tensor-internals or metrics knowledge required. The code under test is pure commonMain Kotlin over Double counters; this is a smoke check, not new implementation.
Size: xs (~30–60 min)
Blocked by: #1229 (F1Score merged to develop), or check out its branch early.

What to do

  1. On a Mac with Xcode installed:
    ./gradlew :skainet-backends:skainet-backend-cpu:iosSimulatorArm64Test --tests "sk.ainet.exec.metrics.*"
  2. If you have a device pipeline, iosArm64 is link-only in CI (no test runner); note
    that on the parent rather than trying to run it.

Then, in every case:

  • Confirm the metric tests (sk.ainet.exec.metrics.*) pass and the values match the JVM run
    bit-for-bit — pure Long counting and Double division, so any drift is itself a finding.
  • Report on #1222: target, toolchain versions, pass/fail, wall-clock, anything
    target-specific you hit (an expect/actual gap, a disabled test source set, a task
    that doesn't exist).

Acceptance

  • Result posted on #1222 with the exact Gradle task(s) run
  • If something is wrong, a separate bug issue opened and linked — don't block the
    parent on investigating it here

Notes

macosArm64Test is the closest sibling if the simulator runtime is missing; run it too
and say which you ran. See Contributing → Build from source for the toolchain setup.

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

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.