Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
  • Is something wrong?
#1,231 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
ios, kotlin
Domain
mobile-dev, testing-qa

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Kotlin
Stars
52
Forks
15
Avg merge
1d 15h
Merged PRs (30d)
36

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SKaiNET-developers/SKaiNET

All issues in SKaiNET-developers/SKaiNET

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.