bench/api.sh exec test fails with curl exit 52, and --ignore-failure still records the timings
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Open bench/api.sh and find the exec step that runs under hyperfine --ignore-failure and POSTs the exec start body with AttachStdout. Confirm the failure by running that step alone against a Kiri Unix socket in WSL2 and checking curl's exit code (52 = empty reply on the upgraded stream). The reporter's workaround is to send {"Detach":true} in the exec start body and to drop --ignore-failure so a failed run is reported rather than timed; done means all 20 iterations pass and a deliberate failure stops the benchmark with an error.
Written by the indexing model from the issue text.
Description
Kiri version and system
Kiri 0.2.1, Windows 11, daemon inside WSL2 (Unix socket)
What you did
Ran the unmodified bench/api.sh against Kiri's Unix socket inside WSL2: 3 warmup + 20 runs.
What happened
All 20 exec iterations fail with curl exit 52. Kiri returns HTTP 101 UPGRADED (AttachStdout:true, exec start body {}), but curl does not complete the upgraded stream.
Because the exec step runs under `hyperfine --ignore-failure`, these failed runs are still timed, so the "API exec" number may measure time-to-failure, not a completed exec.
What you expected instead
The exec step completes successfully, or, if it fails, the benchmark reports the failure instead of timing it.
Anything else
Workaround: sending {"Detach":true} in the exec start body makes all 20 iterations pass (median 27.45 ms, p95 35.21 ms).
Suggestion: use Detach:true (or handle the upgraded stream) and drop --ignore-failure for this step.
bench/api.sh is unchanged on main as of today.
- Dominant language
- Rust
- Stars
- 7.5k
- Forks
- 329
- Avg merge
- 14h 18m
- Merged PRs (30d)
- 204
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from libracoder/kiri
-
VM never idles to sleep while the Windows GUI is open (GUI /info polling resets the idle timer)Openbug
Difficulty 3/5 Half a day Newbie friendliness 68/100
libracoder/kiri#668 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 70/100
libracoder/kiri#654 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
libracoder/kiri#649 ·
Maintainers usually reply within 1 day
-
`kiri-nfs` exposes container `/sys` and `/proc` symlinks as directories, causing infinite directory loops and 100% CPU spikesPossibly taken @talaatmagdyx claimed this today. Openbug
Difficulty 4/5 3-5 days Newbie friendliness 28/100
libracoder/kiri#648 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
libracoder/kiri#647 ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
antithesishq/bombadil#473 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 5 days
-
autofixer: follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
tursodatabase/turso#12217 ·
Maintainers usually reply within 1 day
-
Declare the CMS schema library in the optional recipients extraPossibly taken A pull request linked to this issue is open or already merged. Openarea:python in-progress
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
yhay81/pyropdf#1005 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day