[Quit Applications] ...doesn't seem to work with raycast beta. doesn't find any applications
Open
Nobody has claimed this yet.
bug
extension
extension: quit-applications
platform: macOS
- Dominant language
- TypeScript
- Stars
- 7.8k
- Forks
- 6.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 442
Description
Extension
https://www.raycast.com/mackopes/quit-applications
Raycast Version
0.61.0.0
OS Version
26.5
Description
Error:
Error: Command timed out after undefined milliseconds: osascript
Timed out
Timeout._onTimeout:exec-utils.js:32:33
---
29: const timeoutPromise = new Promise((_resolve, reject) => {
30: timeoutId = setTimeout(() => {
31: spawned.kill("SIGTERM");
32: reject(Object.assign(new Error("Timed out"), { timedOut: true, signal: "SIGTERM" }));
33: }, timeout);
34: });
35: const safeSpawnedPromise = spawnedPromise.finally(() => {
---
listOnTimeout:timers:585:17
process.processTimers:timers:521:7
Steps To Reproduce
The beta doesn't seem compatible,. Can't execute any app searcjh
Current Behaviour
No response
Expected Behaviour
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Quit Applications extension failure against Raycast 0.61.0.0 on the reported OS version, then inspect the osascript timeout at exec-utils.js:32:33. Done means application search and execution work without the timeout; the issue does not identify the extension source file or a failing test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, typescript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100