starred/electerm

Fork 0

mirror of https://github.com/electerm/electerm.git synced 2026-04-25 21:45:56 +03:00

[GH-ISSUE #1062] sftp error #616

New issue

Closed

opened 2026-02-27 00:00:16 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 00:00:16 +03:00

Owner

Originally created by @blue-bird1 on GitHub (Jan 2, 2019).
Original GitHub issue: https://github.com/electerm/electerm/issues/1062

Electerm version:

26.10

Operating system(linux, macos, or windows7/8/10?):

windows10

Expected Behavior

sftp available

Current Behavior

Will be wrong when the terminal is open

Possible Solution

Just need to restart because this is due to unexpected behavior

Steps to Reproduce

1.open a ssh. wait it timeout error
2.open sftp, unavailable
3.reload
4.Sftp is still unavailable

Context (Environment)

Detailed Description

When opening a timeout terminal sftp will cause WebSocket is already in CLOSING or CLOSED state.
If reload now, componentWillUnmount that will trigger the sftp component. will cause WebSocket is already in CLOSING or CLOSED state.
in new terminal this.initData().->this.localList() will cause WebSocket is already in CLOSING or CLOSED state.
Should be accidentally reused for closed websocket

Suggestions?

Originally created by @blue-bird1 on GitHub (Jan 2, 2019). Original GitHub issue: https://github.com/electerm/electerm/issues/1062  ## Electerm version: 26.10 ## Operating system(linux, macos, or windows7/8/10?): windows10 ## Expected Behavior  sftp available ## Current Behavior  Will be wrong when the terminal is open ## Possible Solution  Just need to restart because this is due to unexpected behavior ## Steps to Reproduce   1.open a ssh. wait it timeout error 2.open sftp, unavailable 3.reload 4.Sftp is still unavailable ## Context (Environment)   ## Detailed Description  When opening a timeout terminal sftp will cause `WebSocket is already in CLOSING or CLOSED state`. If reload now,` componentWillUnmount` that will trigger the sftp component. will cause `WebSocket is already in CLOSING or CLOSED state`. in new terminal `this.initData()`.->`this.localList()` will cause `WebSocket is already in CLOSING or CLOSED state`. Should be accidentally reused for closed websocket ## Suggestions?

kerem

2026-02-27 00:00:16 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 00:00:17 +03:00

Author

Owner

@zxdong262 commented on GitHub (Apr 16, 2019):

Should be fixed now, feel free to reopen it if you still experience this.

@zxdong262 commented on GitHub (Apr 16, 2019): Should be fixed now, feel free to reopen it if you still experience this.

kerem commented

2026-02-27 00:00:17 +03:00

Author

Owner

@blue-bird1 commented on GitHub (Apr 27, 2019):

in 0.27.12 Still have this problem.
electerm.0.27.12-465b468a449339cf6565e53f1b2c446ae6c7bf33.js:16 WebSocket is already in CLOSING or CLOSED state. Vo.r.s @ electerm.0.27.12-465b468a449339cf6565e53f1b2c446ae6c7bf33.js:16

@blue-bird1 commented on GitHub (Apr 27, 2019): in 0.27.12 Still have this problem. `electerm.0.27.12-465b468a449339cf6565e53f1b2c446ae6c7bf33.js:16 WebSocket is already in CLOSING or CLOSED state. Vo.r.s @ electerm.0.27.12-465b468a449339cf6565e53f1b2c446ae6c7bf33.js:16`

kerem commented

2026-02-27 00:00:17 +03:00

Author

Owner

@zxdong262 commented on GitHub (Nov 15, 2019):

@blue-bird1 How about now?

@zxdong262 commented on GitHub (Nov 15, 2019): @blue-bird1 How about now?

kerem commented

2026-02-27 00:00:17 +03:00

Author

Owner

@blue-bird1 commented on GitHub (Nov 15, 2019):