search

vitorgalvao / alfred-workflows

Collection of Alfred workflows
BSD 3-Clause "New" or "Revised" License
2.44k stars 167 forks source link

QuitArena failing to quit apps #133

Closed volt4ire closed 3 years ago

volt4ire commented 3 years ago

Setup info

Description of issue

Oftentimes QuitArena fails to quit any programs when invoked. I am running the latest version of Alfred, QuitArena, and macOS. Can you please help me diagnose this? Thanks for your time and all your awesome workflows!!

Debugger output

[09:15:26.933] Logging Started...
[09:16:11.063] QuitArena[Keyword] Processing complete
[09:16:11.068] QuitArena[Keyword] Passing output '' to Run Script
[09:16:11.585] ERROR: QuitArena[Run Script] /Users/rwbarat/Library/Caches/com.runningwithcrayons.Alfred/Workflow Scripts/DAE9F815-4429-4B6B-9757-8DD715459650: execution error: Error: Error: User canceled. (-128)
[09:16:11.591] QuitArena[Run Script] Processing complete
[09:16:11.592] QuitArena[Run Script] Passing output '' to Run Script
vitorgalvao commented 3 years ago

Thank you for the kind words.

execution error: Error: Error: User canceled. (-128)

Any idea what happened there?

What are your values for the Workflow Environment Variables? How are you invoking QuitArena?

volt4ire commented 3 years ago

Thanks for your help!

Any idea what happened there?

I'm not sure what is causing this

What are your values for the Workflow Environment Variables? How are you invoking QuitArena?

I'm invoking it through the keyword ("qapps") and these are my environment variables: image

vitorgalvao commented 3 years ago

Unfortunately, that doesn’t give us more details. The fact it only happens sometimes and you’re the only one experiencing this suggests it’s something in your setup.

Due to the error message, I’d say one the apps may have unsaved changes and is thus refusing to quit. Like I say in the README:

Note both options ask the apps to exit (SIGTERM) instead of telling them (SIGKILL). If you need to force individual processes to terminate, use ProcessControl instead.

So I’d start by looking into that next time it happens. If you can find a way to reproduce the problem reliably and it is indeed a bug, let me know and I’ll reopen.