Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Explain and recover from a quarantined ScreenCaptureKit gate

Geschlossen
  • Stimmt etwas nicht?
#16 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
25/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
macos, swift
Bereich
desktop, devtools

Rechercherichtung

Start with ScreenCaptureKitCaptureGate and the per-user lock at $TMPDIR/boo.peekaboo.sckit-capture.lock, then the code path where desktop_inspect falls back to the CGWindowList capture. Check how the quarantine error and the refusal message are produced, and how the 1 s apps budget is enforced. Done means the refusal explains a temporary conflict with a retry hint, inspection falls back to CGWindowList when ScreenCaptureKit is quarantined, and the lock design is settled with maintainers.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Found in the Ace desktop tools study (githubnext/ace#427), D3c on Canary 0.0.46+684262d, 2026-10-15 at about 14:55 EDT.

Observed: in the middle of a run, after a desktop_menu File → New, every desktop_inspect failed with DESKTOP_ERROR: Capture failed: ScreenCaptureKit is quarantined after an abandoned SCShareableContent.fetchWindowForWindowID call. desktop_apps timed out against its 1.00 s observation budget, and another call returned The operation couldn't be completed. Operation timed out. The agent stopped safely and typed nothing. A few minutes later, inspect worked again through the CGWindowList engine (capture.window 770 ms), and apps took 955 ms, close to its 1 s budget.

Likely cause: Peekaboo coordinates ScreenCaptureKit across processes with a per-user lock at $TMPDIR/boo.peekaboo.sckit-capture.lock (ScreenCaptureKitCaptureGate). At the same time, a separate process on the Mac was running Peekaboo's AutomationKit tests (the patch test run for the pin bump), which do real captures. Any two Peekaboo users on one Mac share that gate and can starve or quarantine each other: Ace dev and Canary, Ace and a Peekaboo CLI, or tests.

Asks:

  • The refusal should say the problem is temporary and caused by another capture, and give a wait-and-retry hint. Today it reads like a broken desktop.
  • When ScreenCaptureKit is quarantined, inspection should fall back to the CGWindowList capture it already uses afterwards, rather than failing.
  • Consider giving the gate a host-specific lock, or one keyed to the host's identity, so separate embedding apps don't block each other. Possibly upstream.
  • The 1 s apps inventory budget leaves no headroom when the Mac is loaded (955 ms when healthy).
Vorherrschende Sprache
Swift
Sterne
0
Forks
0
Ø Merge
19 Min.
Gemergte PRs (30 T.)
107

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus githubnext/desktop-tools

Alle Issues in githubnext/desktop-tools

Ähnliche Issues

Weitere Issues zu Swift

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.