Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Explain and recover from a quarantined ScreenCaptureKit gate

Fermée
  • Quelque chose ne va pas ?
#16 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
25/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
macos, swift
Domaine
desktop, devtools

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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).
Langage dominant
Swift
Étoiles
0
Forks
0
Merge moyen
19 min
PR mergées (30 j)
107

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de githubnext/desktop-tools

Toutes les issues de githubnext/desktop-tools

Issues similaires

Plus d'issues Swift

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.