Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Error when starting Atom from terminal

Abierto
  • ¿Algo no está bien?
#189 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
javascript, python
Área
devtools

Línea de trabajo

Reproduce el fallo iniciando Atom con atom .; después, inspecciona las entradas de la pila de ide-python alrededor de python/lib/utils.js y python/lib/main.js, especialmente detectPipEnv. Compara los entornos de lanzamiento del terminal y del escritorio; se considera terminado cuando el inicio desde el terminal ya no produce spawn ENOTDIR y los paquetes del entorno virtual siguen estando disponibles.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Hey,
I have the follow error when opening atom from the terminal with atom .
Once atom is opened, every time a open a python module I get the error.

internal/child_process.js:358 Uncaught (in promise) Error: spawn ENOTDIR
    at ChildProcess.spawn (internal/child_process.js:358)
    at Object.spawn (child_process.js:543)
    at resolve (/home/somnium/.atom/…thon/lib/utils.js:9)
    at new Promise (<anonymous>)
    at detectPipEnv (/home/somnium/.atom/…thon/lib/utils.js:8)
    at PythonLanguageClient.startServerProcess (/home/somnium/.atom/…thon/lib/main.js:50)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:298)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at process.reportBusyWhile (auto-languageclient.ts:298)
    at AtomIdeProvider.<anonymous> (atom-ide-provider.js? [sm]:7)
    at Generator.next (<anonymous>)
    at step (/home/somnium/.atom/…m-ide-provider.js:9)
    at /home/somnium/.atom/…m-ide-provider.js:9
    at new Promise (<anonymous>)
    at AtomIdeProvider.<anonymous> (/home/somnium/.atom/…m-ide-provider.js:9)
    at Object.reportBusyWhile (index.js? [sm]:33)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:798)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at PythonLanguageClient.AutoLanguageClient.reportBusyWhile (auto-languageclient.ts:796)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:296)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at PythonLanguageClient.startServer (auto-languageclient.ts:295)
    at ServerManager._serverManager.server_manager_js_1.ServerManager [as _startServer] (auto-languageclient.ts:253)
    at ServerManager.<anonymous> (server-manager.ts:155)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…server-manager.js:7
    at new Promise (<anonymous>)
internal/child_process.js:358 Uncaught (in promise) Error: spawn ENOTDIR
    at ChildProcess.spawn (internal/child_process.js:358)
    at Object.spawn (child_process.js:543)
    at resolve (/home/somnium/.atom/…thon/lib/utils.js:9)
    at new Promise (<anonymous>)
    at detectPipEnv (/home/somnium/.atom/…thon/lib/utils.js:8)
    at PythonLanguageClient.startServerProcess (/home/somnium/.atom/…thon/lib/main.js:50)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:298)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at process.reportBusyWhile (auto-languageclient.ts:298)
    at AtomIdeProvider.<anonymous> (atom-ide-provider.js? [sm]:7)
    at Generator.next (<anonymous>)
    at step (/home/somnium/.atom/…m-ide-provider.js:9)
    at /home/somnium/.atom/…m-ide-provider.js:9
    at new Promise (<anonymous>)
    at AtomIdeProvider.<anonymous> (/home/somnium/.atom/…m-ide-provider.js:9)
    at Object.reportBusyWhile (index.js? [sm]:33)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:798)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at PythonLanguageClient.AutoLanguageClient.reportBusyWhile (auto-languageclient.ts:796)
    at PythonLanguageClient.<anonymous> (auto-languageclient.ts:296)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…languageclient.js:7
    at new Promise (<anonymous>)
    at __awaiter (/home/somnium/.atom/…languageclient.js:3)
    at PythonLanguageClient.startServer (auto-languageclient.ts:295)
    at ServerManager._serverManager.server_manager_js_1.ServerManager [as _startServer] (auto-languageclient.ts:253)
    at ServerManager.<anonymous> (server-manager.ts:155)
    at Generator.next (<anonymous>)
    at /home/somnium/.atom/…server-manager.js:7
    at new Promise (<anonymous>)

Everything works if I'm starting Atom from desktop icon, however I need to be able to running it from the terminal.
When running sudo atom . it works, but I don't get my virtual env installed packages available which makes it impossible to use some other atom plugins features.

My setup:
OS: Ubuntu 18
Atom: 1.42
ide-python: 1.5.0

Any help is welcome.
Thanks

Lenguaje dominante
JavaScript
Estrellas
238
Forks
41
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de atom-community/ide-python

Todos los issues de atom-community/ide-python

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.