redhat-developer / redhat-developer/vscode-java
stream error while trying to build vscode-java@1.7.0
还没有人认领这个 Issue。
- 主要语言
- TypeScript
- 星标
- 2.3k
- 派生
- 546
- 平均合并
- 20 小时 1 分钟
- 30 天内合并 PR
- 11
描述
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 ?
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
使用 CONTRIBUTING.md、npm install、gulp download_server 和 vsce package 重现本地构建,然后启动生成的 .vsix。首先检查从 plugins/redhat-java-features/extension/dist/extension.js 报告的 stream 错误;当本地构建的扩展能够在没有 EPIPE 或 ERR_STREAM_DESTROYED 错误的情况下启动时,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- java, typescript, vscode
- 领域
- devtools
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100