redhat-developer / redhat-developer/vscode-java
stream error while trying to build vscode-java@1.7.0
Nessuno ha ancora preso questa issue.
- Lingua principale
- TypeScript
- Stelle
- 2.3k
- Fork
- 546
- Merge medio
- 20h 1m
- PR unite (30g)
- 11
Descrizione
Getting Cannot call write after a stream was destroyed error while trying to use vscode-java@1.7.0 which I built locally
Environment
- Operating System: macOS Catalina
- JDK version: java version "1.8.0_281" and Java(TM) SE Runtime Environment (build 1.8.0_281-b09)
- Visual Studio Code version: 1.69
- Java extension version: 1.7.0
Steps To Reproduce
I have built vscode-java@1.7.0 locally by following the instructions here: https://github.com/redhat-developer/vscode-java/blob/v1.7.0/CONTRIBUTING.md
- For Client side setup, cloned the vscode-java and checked out to v1.7.0 and then ran
npm install - For Server side setup, just download the latest snapshot by running the command
./node_modules/.bin/gulp download_server - Then ran
vsce packagewhich generated a .vsix file - Trying to launch the built extension which results with the following error:
Current Result
plugins/redhat-java-features/extension/dist/extension.js:2:1044055
root ERROR [hosted-plugin: 15563] Promise rejection not handled in one second: Error: write EPIPE , reason: Error: write EPIPE
With stack trace: Error: write EPIPE
at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:94:16)
root ERROR [hosted-plugin: 15563] Promise rejection not handled in one second: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed , reason: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
root ERROR [hosted-plugin: 15563] With stack trace: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at doWrite (_stream_writable.js:399:19)
at writeOrBuffer (_stream_writable.js:387:5)
at Socket.Writable.write (_stream_writable.js:318:11)
In addition, the extension keeps on loading without showing any syntax errors.
How to resolve this issue ?
Please point me if I am building it incorrectly ?
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Riproduci la build locale usando CONTRIBUTING.md, npm install, gulp download_server e vsce package, quindi avvia il .vsix generato. Inizia esaminando gli errori di stream segnalati da plugins/redhat-java-features/extension/dist/extension.js; il lavoro è completato quando l’estensione compilata localmente si avvia senza gli errori EPIPE o ERR_STREAM_DESTROYED.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java, typescript, vscode
- Ambito
- devtools
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100