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
I have run q doctor in the affected terminal session
I have run q restart and 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!
I can reproduce the issue, one way to resolve it temporarily is to manually run qterm inside of tmux, that will launch out process which should make it work..
Checks
q doctor
in the affected terminal sessionq restart
and replicated the issue againOperating 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 errorsSteps to reproduce
tmux
on remote to open an session.Environment
The text was updated successfully, but these errors were encountered: