Notes de version

Cette documentation décrit le périmètre figé de la préversion expérimentale v0.0.18. La publication effective et les téléchargements sont consignés dans GitHub Releases.

Les compléments v0.0.18 ci-dessous sont actuellement en anglais ; le reste de la traduction est conservé. English · 简体中文

v0.0.18 release scope and known limits

This release freezes already implemented and verified functionality. It remains an experimental prerelease, not a production-readiness claim. The v0.0.18 Release is the authority for actual publication, assets and checksums; a skipped publishing job is not release evidence.

• JSON keeps the previous implementation as its default. json.encode / json.decode share the stringify / parse entry points. The float round-trip correction for 1e20 is included; yyjson replacement and performance exploration have ended.
• Task/native async support remains the documented bounded subset. Shutdown admission and cleanup fixes do not imply a complete M:N runtime or universal network suspension.
• HTTP uses bounded socket readiness, queues and response handling, with keep-alive support and optional bounded diagnostic records. These changes do not imply that all workload acceptance has passed.
• ku supervise controls whole-program workers, admission, queue bytes, output and cleanup. It is not one worker per HTTP request or per Task, and it is not automatically applied to ordinary ku run.

Known HTTP issue: HTTP 504 occurred historically, including a seven-request cluster. This round’s 60-second and 180-second short tests did not reproduce it. The root cause is unconfirmed, and formal 30-minute stability acceptance has not passed. It is retained as a known issue for v0.0.18 and is not a separate release blocker. The earliest three historical 504s lack enough evidence for a unique reconstruction.

Deferred, not completed: complete M:N, general Task network scheduling, the complete database platform matrix, and further long-running workload acceptance belong to later versions.

Process memory boundary

Host	ku supervise guarantee and prerequisite
Linux	cgroup v2 kernel charged memory; a writable, delegated domain root with memory and pids enabled is required. Required interfaces include memory.max, memory.swap.max, memory.oom.group, pids.max and cgroup.kill. Missing controls or permissions cause refusal before application execution.
Windows	Nested Job Object limits for individual workers and the worker group, measured as committed virtual memory, not RSS. Initial process commit is checked before its suspended application thread is released. Host policy can reject Job assignment.
macOS	This isolation mode is not supported natively and is explicitly rejected before starting the application. Use a suitably configured Linux host/VM when required; there is no automatic VM bridge.

Worker accounting covers applicable Ku and third-party library allocations in that worker’s resource domain. Linux cgroup accounting and Windows commit are different metrics. Linux memory.max may permit transient overshoot; these mechanisms do not promise an absolute ceiling on all physical memory at every instant.

The coordinator itself has no OS memory hard limit. Its bounded admission/control reserve is an accounting policy, not a coordinator RSS limit. A single Task’s entire heap is not precisely metered; shared connection pools, caches and library allocations cannot be exactly attributed to each Task. External databases, the host/VM and build compilers lie outside the worker domain.

When an OS limit terminates a worker, the coordinator reports failure and only returns reserved capacity after confirmed cleanup. Some allocation failures can be reported before allocation, but third-party exhaustion is not guaranteed to become an ordinary Result. Database operations are never automatically retried; an exited worker does not prove rollback, and side effects may be unknown.

See the process execution contract, concurrency contract and HTTP acceptance record. Cross-platform CI and installation checks establish only their reported targets and scope, not a completed real-database matrix.

v0.0.17 · Préversion expérimentale

Publiée le 2026-10-18 (America/Los_Angeles), soit 2026-10-19T03:51:10Z en UTC. La version possède prerelease=true et draft=false. Aucune version stable n’a actuellement été vérifiée.

Principaux changements :

• Les paramètres empruntés synchrones en lecture seule utilisent &name: T, avec des arguments d’appel ordinaires. Les paramètres possédés normaux conservent la sémantique de déplacement.
• Le sous-ensemble du parser auto-hébergé ajoute while avec accolades, avec une profondeur d’imbrication et un nombre d’instructions bornés.
• Les tests multiplateformes corrigent les vérifications de déconnexion de stdout. Cela n’ajoute aucune API métier.
• Les archives incluent les dépendances Rust correspondantes pour le lanceur par défaut et un paquet TLS cible. Des chaînes d’outils externes adaptées restent nécessaires.

Les téléchargements couvrent Windows x64, Linux x64 et macOS arm64. Les sept fichiers de la version sont trois archives de plateforme, trois manifestes et SHA256SUMS. Voir l’installation et les notes de version complètes.

Compatibilité et limites

Ku reste expérimental et n’est pas prêt pour la production. La version 0.0.x ne promet pas de compatibilité des sources ou de l’ABI C/FFI générée. Recompilez les artefacts natifs concernés lors des mises à jour. Les paramètres async empruntés, l’auto-hébergement complet et l’async natif complet sont hors du périmètre de cette version.

Le lanceur par défaut n’embarque que le source d’entrée ; les modules importés exigent toujours leurs emplacements d’origine. Les clients de bases sont natifs uniquement. Vérifiez les limites de serveur réel, TLS et état de session de chaque pilote. Le code propre à Ku ne bénéficie toujours d’aucune concession de licence open source.