aws / aws/amazon-q-developer-cli
Cann't run in tmux
Abierto
Nadie ha tomado este issue todavía.
bug
os:linux
- Lenguaje dominante
- Rust
- Estrellas
- 2k
- Forks
- 439
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Checks
- I have searched github.com/aws/amazon-q-developer-cli/issues and there are no duplicates of my issue
- I have run
q doctorin the affected terminal session - I have run
q restartand replicated the issue again
Operating system
Linux 5.10.230-202.885.amzn2int.x86_64 - Amazon Linux 2
Expected behaviour
Amazon Q Cli completions should run as normal in tmux session.
Actual behaviour
Not run and q doctor reports errors
❯ q doctor
✘ Qterm Socket Check: Socket exists but could not connect: Connection refused (os error 111)
✘ Doctor found errors. Please fix them and try again.
If you are not sure how to fix it, please open an issue with q issue to let us know!
Steps to reproduce
- Install Amazon Q locally.
- Enable ssh integration.
- Amazon Q runs successfully on remote.
- Execute
tmuxon remote to open an session. - Use as normal
Environment
[q-details]
version = "1.6.0"
hash = "6d13844d6546a5c29e7e121450af1130eb189e7f"
date = "2025-01-09T00:46:48.09362Z (2d ago)"
variant = "minimal"
[system-info]
chip = "AMD EPYC 9R14"
total-cores = 64
memory = "246.40 GB"
[system-info.os.linux]
kernel_version = "5.10.230-202.885.amzn2int.x86_64"
id = "amzn"
name = "Amazon Linux"
pretty_name = "Amazon Linux 2"
version_id = "2"
version = "2"
variant = "internal"
[environment]
cwd = "/local/home/USER"
cli-path = "/local/home/USER"
os = "Linux"
shell-path = "/local/home/USER/.toolbox/tools/toolbox/1.1.1651.0/toolbox-exec"
shell-version = "5.8"
install-method = "toolbox"
in-ssh = true
[env-vars]
PATH = "/home/USER/.local/share/mise/installs/node/18.20.2/bin:/home/USER/.local/share/mise/installs/python/3.12.7/bin:/home/USER/.local/share/mise/installs/python/3.11.10/bin:/home/USER/.local/share/mise/installs/python/3.10.15/bin:/home/USER/.local/share/mise/installs/python/3.9.20/bin:/home/USER/.local/share/mise/installs/python/3.8.20/bin:/home/USER/.local/share/mise/installs/ruby/2.7.8/bin:/home/USER/.toolbox/bin:/usr/lib/jvm/java-17-amazon-corretto.x86_64/bin:/home/USER/.toolbox/bin:/usr/lib/jvm/java-17-amazon-corretto.x86_64/bin:/home/USER/.cargo/bin:/usr/local/bin:/usr/bin:/home/USER/bin:/usr/local/sbin:/usr/sbin:/home/USER/.local/bin:/home/USER/bin:/apollo/env/envImprovement/bin:/apollo/env/AmazonAwsCli/bin/:/home/USER/bin:/apollo/env/envImprovement/bin:/apollo/env/AmazonAwsCli/bin/"
QTERM_SESSION_ID = "4219d93f89bd4b9d963b4f09861e11f5"
Q_PARENT = "/tmp/q-parent-92e543f5b978
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza reproduciendo el fallo en una sesión SSH después de abrir tmux y, a continuación, ejecuta q doctor y q restart como se describe. Investiga el error de conexión rechazada del socket de Qterm; se considera completado cuando las finalizaciones de Amazon Q funcionan dentro de tmux y q doctor no informa de ningún error.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- linux
- Área
- cli, operating-systems
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 35/100