Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Atom-Typescript error: Cannot call write after a stream was destroyed #1607

Open
anupam-basu opened this issue Mar 21, 2022 · 0 comments
Open

Comments

@anupam-basu
Copy link

[Enter steps to reproduce:]

  1. ...
  2. ...

Atom: 1.59.0 x64
Electron: 9.4.4
OS: Unknown macOS version
Thrown From: atom-typescript package 14.4.0

Stack Trace

Atom-Typescript error: Cannot call write after a stream was destroyed

At Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed

Error [ERR_STREAM_DESTROYED] [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
    at doWrite (_stream_writable.js:431:19)
    at writeOrBuffer (_stream_writable.js:419:5)
    at Socket.Writable.write (_stream_writable.js:309:11)
    at dn.execute (/packages/atom-typescript/dist/main.js:9:111609)
    at Qc.getErr (/packages/atom-typescript/dist/main.js:9:283164)
    at Qc.init (/packages/atom-typescript/dist/main.js:9:281400)

Commands

     -0:37.6.0 intentions:highlight (input.hidden-input)
     -0:37.4.0 core:copy (input.hidden-input)
     -0:37.1.0 find-and-replace:show (input.hidden-input)
     -0:36.8.0 core:paste (input.hidden-input)
  3x -0:36.5.0 core:confirm (input.hidden-input)

Non-Core Packages

atom-clock 0.1.18 
atom-material-ui 2.1.3 
atom-typescript 14.4.0 
busy-signal 2.0.1 
ide-typescript 0.9.5 
intentions 2.1.1 
linter 3.4.0 
linter-eslint 9.0.0 
linter-ui-default 3.4.1 
python-autopep8 0.1.3 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant