Version Packages#64
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
kit@2.14.0
Minor Changes
b5f722c: host: detect CPU steal at callback-deadline kills (detection only)
The per-callback kill switch is wall-clock only, and a true fuel/instruction
budget is impossible on this stack (wazero v1.12.0 / extism v1.7.1 expose no
fuel/epoch/gas metering API). So a CPU-steal-throttled VM can blow the deadline
on a guest running pure, well-behaved guest code, and that kill is booked as a
fault that can quarantine a healthy game.
This change MEASURES host-stolen CPU at the kill site and records it alongside
the existing deadline metric — detection only, no behavior change:
aggregate hypervisor-STEAL field (Linux; a no-op ok=false stub elsewhere),
sampled at callback BOUNDARIES, never per-instruction. cgroup throttling is
deliberately NOT read: steal blames the host (the eventual exonerate case),
whereas cgroup throttle blames the guest (a runaway you must not exonerate).
StealMetricsextension interface is recorded viaa type assertion at the wall-clock-kill site, so existing Metrics implementers
compile and run unchanged. fault(), quarantine, and End() are untouched; the
existing GameCallbackDeadline record is never replaced or suppressed.