You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As soon as I open it in pycharm, Github DESKTOP crash and get the following error, no problem when I switch to another editor:
`Error: spawn C:\Program Files\JetBrains\PyCharm 2023.2\bin\pycharm64.exe EACCES
at __node_internal_captureLargerStackTrace (node:internal/errors:490:5)
at __node_internal_errnoException (node:internal/errors:620:12)
at Process.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:476:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Version: 3.3.5
OS: Windows 10.0.22621`
Release version
3.3.5
Operating system
Windows 10.0.22621
Steps to reproduce the behavior
1.open it in pycharm
Log files
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hey @renhai-lab thanks for the issue. It looks like there is a permission issue.
GitHub Desktop doesn't have permission to start pycharm64.exe. You can try to run GitHub Desktop with a proper user (with access to the PyCharm executable) or try to "Run as Administrator".
The problem
As soon as I open it in pycharm, Github DESKTOP crash and get the following error, no problem when I switch to another editor:
`Error: spawn C:\Program Files\JetBrains\PyCharm 2023.2\bin\pycharm64.exe EACCES
at __node_internal_captureLargerStackTrace (node:internal/errors:490:5)
at __node_internal_errnoException (node:internal/errors:620:12)
at Process.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:476:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Version: 3.3.5
OS: Windows 10.0.22621`
Release version
3.3.5
Operating system
Windows 10.0.22621
Steps to reproduce the behavior
1.open it in pycharm
Log files
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: