Repository navigation
Bump version to 0.50.0 - #88
Closed
lawrencecchen wants to merge 1 commit into
Closed
lawrencecchen wants to merge 1 commit into
lawrencecchen wants to merge 1 commit into
Conversation
Contributor
Preview Videos and ScreenshotsOpen Workspace (1 hr expiry) · Open Dev Browser (1 hr expiry) · Open Diff Heatmap Screenshot capture was skipped.
Generated by manaflow preview system |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
lawrencecchen
added a commit
that referenced
this pull request
Oct 2, 2026
closing_one_hundred_terminals_updates_the_tree_at_once_and_ends_every_host stalls about 2 s at fixed points (closes #71, #72, #88, #99 in probe runs 36951324179, 36953259790, 36953266201, 36951369512; it also did so before the host frame reader landed). Daemon probes showed each stall is a SetKittyGraphicsLimits request on a mux-deadline worker that waits the full 2 s CONTROL_RESPONSE_TIMEOUT and fails, at Kitty budget bucket changes. The terminal's reader received ResyncRequired for every update and never the KittyGraphicsLimitsAck. The request holds the terminal's runtime lock while it waits, so a close of that terminal waits too. Reproduced locally with the hosted binary: closing 17 terminals stalls one close for about 2.0 s in 3 of 3 runs (bucket 32 -> 8). The test closes 17 terminals and requires every close-terminal reply under 1 s. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
lawrencecchen
added a commit
that referenced
this pull request
Oct 2, 2026
closing_one_hundred_terminals_updates_the_tree_at_once_and_ends_every_host stalls about 2 s at fixed points (closes #71, #72, #88, #99 in probe runs 36951324179, 36953259790, 36953266201, 36951369512; it also did so before the host frame reader landed). Daemon probes showed each stall is a SetKittyGraphicsLimits request on a mux-deadline worker that waits the full 2 s CONTROL_RESPONSE_TIMEOUT and fails, at Kitty budget bucket changes. The terminal's reader received ResyncRequired for every update and never the KittyGraphicsLimitsAck. The request holds the terminal's runtime lock while it waits, so a close of that terminal waits too. Reproduced locally with the hosted binary: closing 17 terminals stalls one close for about 2.0 s in 3 of 3 runs (bucket 32 -> 8). The test closes 17 terminals and requires every close-terminal reply under 1 s. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
lawrencecchen
added a commit
that referenced
this pull request
Oct 2, 2026
closing_one_hundred_terminals_updates_the_tree_at_once_and_ends_every_host stalls about 2 s at fixed points (closes #71, #72, #88, #99 in probe runs 36951324179, 36953259790, 36953266201, 36951369512; it also did so before the host frame reader landed). Daemon probes showed each stall is a SetKittyGraphicsLimits request on a mux-deadline worker that waits the full 2 s CONTROL_RESPONSE_TIMEOUT and fails, at Kitty budget bucket changes. The terminal's reader received ResyncRequired for every update and never the KittyGraphicsLimitsAck. The request holds the terminal's runtime lock while it waits, so a close of that terminal waits too. Reproduced locally with the hosted binary: closing 17 terminals stalls one close for about 2.0 s in 3 of 3 runs (bucket 32 -> 8). The test closes 17 terminals and requires every close-terminal reply under 1 s. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
lawrencecchen
added a commit
that referenced
this pull request
Oct 2, 2026
closing_one_hundred_terminals_updates_the_tree_at_once_and_ends_every_host stalls about 2 s at fixed points (closes #71, #72, #88, #99 in probe runs 36951324179, 36953259790, 36953266201, 36951369512; it also did so before the host frame reader landed). Daemon probes showed each stall is a SetKittyGraphicsLimits request on a mux-deadline worker that waits the full 2 s CONTROL_RESPONSE_TIMEOUT and fails, at Kitty budget bucket changes. The terminal's reader received ResyncRequired for every update and never the KittyGraphicsLimitsAck. The request holds the terminal's runtime lock while it waits, so a close of that terminal waits too. Reproduced locally with the hosted binary: closing 17 terminals stalls one close for about 2.0 s in 3 of 3 runs (bucket 32 -> 8). The test closes 17 terminals and requires every close-terminal reply under 1 s. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
lawrencecchen
added a commit
that referenced
this pull request
Oct 2, 2026
closing_one_hundred_terminals_updates_the_tree_at_once_and_ends_every_host stalls about 2 s at fixed points (closes #71, #72, #88, #99 in probe runs 36951324179, 36953259790, 36953266201, 36951369512; it also did so before the host frame reader landed). Daemon probes showed each stall is a SetKittyGraphicsLimits request on a mux-deadline worker that waits the full 2 s CONTROL_RESPONSE_TIMEOUT and fails, at Kitty budget bucket changes. The terminal's reader received ResyncRequired for every update and never the KittyGraphicsLimitsAck. The request holds the terminal's runtime lock while it waits, so a close of that terminal waits too. Reproduced locally with the hosted binary: closing 17 terminals stalls one close for about 2.0 s in 3 of 3 runs (bucket 32 -> 8). The test closes 17 terminals and requires every close-terminal reply under 1 s. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
lawrencecchen
added a commit
that referenced
this pull request
Oct 2, 2026
closing_one_hundred_terminals_updates_the_tree_at_once_and_ends_every_host stalls about 2 s at fixed points (closes #71, #72, #88, #99 in probe runs 36951324179, 36953259790, 36953266201, 36951369512; it also did so before the host frame reader landed). Daemon probes showed each stall is a SetKittyGraphicsLimits request on a mux-deadline worker that waits the full 2 s CONTROL_RESPONSE_TIMEOUT and fails, at Kitty budget bucket changes. The terminal's reader received ResyncRequired for every update and never the KittyGraphicsLimitsAck. The request holds the terminal's runtime lock while it waits, so a close of that terminal waits too. Reproduced locally with the hosted binary: closing 17 terminals stalls one close for about 2.0 s in 3 of 3 runs (bucket 32 -> 8). The test closes 17 terminals and requires every close-terminal reply under 1 s. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
lawrencecchen
added a commit
that referenced
this pull request
Oct 2, 2026
closing_one_hundred_terminals_updates_the_tree_at_once_and_ends_every_host stalls about 2 s at fixed points (closes #71, #72, #88, #99 in probe runs 36951324179, 36953259790, 36953266201, 36951369512; it also did so before the host frame reader landed). Daemon probes showed each stall is a SetKittyGraphicsLimits request on a mux-deadline worker that waits the full 2 s CONTROL_RESPONSE_TIMEOUT and fails, at Kitty budget bucket changes. The terminal's reader received ResyncRequired for every update and never the KittyGraphicsLimitsAck. The request holds the terminal's runtime lock while it waits, so a close of that terminal waits too. Reproduced locally with the hosted binary: closing 17 terminals stalls one close for about 2.0 s in 3 of 3 runs (bucket 32 -> 8). The test closes 17 terminals and requires every close-terminal reply under 1 s. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
lawrencecchen
added a commit
that referenced
this pull request
Oct 2, 2026
closing_one_hundred_terminals_updates_the_tree_at_once_and_ends_every_host stalls about 2 s at fixed points (closes #71, #72, #88, #99 in probe runs 36951324179, 36953259790, 36953266201, 36951369512; it also did so before the host frame reader landed). Daemon probes showed each stall is a SetKittyGraphicsLimits request on a mux-deadline worker that waits the full 2 s CONTROL_RESPONSE_TIMEOUT and fails, at Kitty budget bucket changes. The terminal's reader received ResyncRequired for every update and never the KittyGraphicsLimitsAck. The request holds the terminal's runtime lock while it waits, so a close of that terminal waits too. Reproduced locally with the hosted binary: closing 17 terminals stalls one close for about 2.0 s in 3 of 3 runs (bucket 32 -> 8). The test closes 17 terminals and requires every close-terminal reply under 1 s. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
lawrencecchen
added a commit
that referenced
this pull request
Oct 2, 2026
closing_one_hundred_terminals_updates_the_tree_at_once_and_ends_every_host stalls about 2 s at fixed points (closes #71, #72, #88, #99 in probe runs 36951324179, 36953259790, 36953266201, 36951369512; it also did so before the host frame reader landed). Daemon probes showed each stall is a SetKittyGraphicsLimits request on a mux-deadline worker that waits the full 2 s CONTROL_RESPONSE_TIMEOUT and fails, at Kitty budget bucket changes. The terminal's reader received ResyncRequired for every update and never the KittyGraphicsLimitsAck. The request holds the terminal's runtime lock while it waits, so a close of that terminal waits too. Reproduced locally with the hosted binary: closing 17 terminals stalls one close for about 2.0 s in 3 of 3 runs (bucket 32 -> 8). The test closes 17 terminals and requires every close-terminal reply under 1 s. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This branch was successfully deployed
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.
Release v0.50.0
Fixed
Build GhosttyKit with universal xcframework target instead of native to avoid M4-tuned code running suboptimally on M1.