En utilisant AWS re:Post, vous acceptez les AWS re:Post Conditions d’utilisation
AWS re:Postre:Post

CodeCatalyst: VS code giving The process tried to write to a nonexistent pipe error when reconnecting to dev environment using remote-ssh

0

VS Code connected to the CodeCatalyst dev environment after setup. Then trying to connect again later after doing a stop I keep on getting the error: [14:32:51.936] Resolver error: Error: The process tried to write to a nonexistent pipe at g.Offline (c:\Users\w7000114\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:642754) at c:\Users\w7000114\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:638710 at t.handleInstallOutput (c:\Users\w7000114\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:639138) at t.tryInstall (c:\Users\w7000114\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:761983) at async c:\Users\w7000114\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:722522 at async t.withShowDetailsEvent (c:\Users\w7000114\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:725828) at async I (c:\Users\w7000114\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:719493) at async t.resolve (c:\Users\w7000114\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:723199) at async c:\Users\w7000114\.vscode\extensions\ms-vscode-remote.remote-ssh-0.107.1\out\extension.js:2:907003 [14:32:51.943]

Sujets
Outils de développementDevOps
Balises
Amazon CodeCatalyst
Langue
English
Amanda
demandé il y a 5 mois172 vues
2 réponses
0

Thank you for reporting the Dev environment issue. I've raised it with our service team, and I'll reach out to you as soon as I have an update.

AWS
EXPERT
Sundaresh_I
répondu il y a 5 mois
0

Hi there! From our initial investigation, it seems like an issue related to the toolkit's session. Could you please provide the version numbers of the toolkit and remote extension you are using to help us investigate further?

As a workaround, our team was able to connect to the dev environment after stopping it by following these steps:

  1. Connect local VSCode to CodeCatalyst.
  2. Open CDE using VSCode Toolkits.
  3. Stop CDE using VSCode Toolkits.
  4. Open CDE using VSCode Toolkits again (it opened in a new window) and connect to it.
AWS
EXPERT
Sundaresh_I
répondu il y a 5 mois

Vous n'êtes pas connecté. Se connecter pour publier une réponse.

Une bonne réponse répond clairement à la question, contient des commentaires constructifs et encourage le développement professionnel de la personne qui pose la question.

Instructions pour répondre aux questions

Contenus pertinents