aws / aws/amazon-q-developer-cli

bug: Q broke SSH

Ouverte
#2,355 1 commentaire 2 réactions 0 personnes assignées Voir sur GitHub
Langage dominant
Rust
Étoiles
2k
Forks
439
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

AL2 remote from macOS

### Expected behaviour

Running git operations should work as usual

### Actual behaviour

```
/home/hazout/.local/share/amazon-q/ssh_inner: line 15: Bad configuration option: setenv
/home/hazout/.local/share/amazon-q/ssh_inner: terminating, 1 bad configuration options
fatal: Could not read from remote repository.
```

### Steps to reproduce

Q is installed on a remote AL2 machine, while I am SSHing into it via macOS terminal.
Running any git related command shows this error. I'm not sure why it's trying to do anything related to Q.

### Environment

```yaml
[q-details]
version = "1.12.6"
hash = "9c083cf7e8f7de077eb116c3993823b82f71ca12"
date = "2025-07-18T21:39:05.889985Z (3d ago)"
variant = "minimal"

[system-info]
chip = "AMD EPYC 7R13 Processor"
total-cores = 16
memory = "123.22 GB"

[system-info.os.linux]
kernel_version = "5.10.238-215.956.amzn2int.x86_64"
id = "amzn"
name = "Amazon Linux"
pretty_name = "Amazon Linux 2"
version_id = "2"
version = "2"
variant = "internal"

[environment]
cwd = "/workplace/USER"
cli-path = "/workplace/USER"
os = "Linux"
shell-path = "/local/home/USER/.toolbox/tools/toolbox/1.1.1986.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.3/bin:/home/USER/.toolbox/bin:/home/USER/.toolbox/bin:/usr/local/bin:/usr/bin:/home/USER/bin:/usr/local/sbin:/usr/sbin:/home/USER/.local/bin:/apollo/env/OdinTools/bin:/apollo/env/envImprovement/bin:/apollo/env/AAAWorkspaceSupport/bin:/apollo/env/ApolloCommandLine/bin:/apollo/env/BarkCLI/bin:/apollo/env/RemoteOverrideSupport/bin:/apollo/env/ScalingPlannerCLI/bin:/apollo/env/TardigradeServiceCoral2Json/bin:/apollo/env/VMAProxyCLI/bin:/apollo/env/WHOFleetTemplates/bin"
Q_PARENT = "/tmp/q-parent-3eb8b71ddb094498a6b69ba672ba5a93.socket"
Q_SET_PARENT_CHECK = "1"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
```

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Reproduisez l’échec en exécutant une opération git depuis un hôte Amazon Linux 2 accessible via macOS SSH, après avoir vérifié `q doctor` et `q restart`. Inspectez `/home/hazout/.local/share/amazon-q/ssh_inner`, en particulier la ligne 15 signalée, et vérifiez que la configuration SSH reste compatible et que les opérations git se terminent sans l’erreur `setenv`.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
git, rust, shell
Domaine
cli, networking
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.