You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug Description:
In the recent version of Theia, a frontendConnectionTimeout parameter has been provided in the backend socket keep-alive mechanism. This parameter is used to set the timeout period for the backend socket to wait for a connection after the frontend socket is disconnected. I have set this timeout period to 5 seconds.When the network connection was interrupted, I started editing a file. When the network was restored, I found that I was unable to close and save that file.
Steps to Reproduce:
1.Opened a file called demo.js.
2.Disconnected the network and made some changes to demo.js. At this point, the file couldn't be saved because the network was disconnected, which is expected.
3.Reconnected the network and noticed that the unsaved changes in demo.js couldn't be saved anymore.
After multiple attempts, it seems that this is because the time taken to reconnect after the network was disconnected was less than 5 seconds. As a result, the backend continued to reuse the old socket, which caused the inability to save the file.
Additional Information:
Operating System: debian docker
Theia Version: 1.47.1
The text was updated successfully, but these errors were encountered:
zhuanshenlikai
changed the title
Some files can not be saved
Some files can not be saved when losing and restoring network connection
May 9, 2024
Bug Description:
In the recent version of Theia, a frontendConnectionTimeout parameter has been provided in the backend socket keep-alive mechanism. This parameter is used to set the timeout period for the backend socket to wait for a connection after the frontend socket is disconnected. I have set this timeout period to 5 seconds.When the network connection was interrupted, I started editing a file. When the network was restored, I found that I was unable to close and save that file.
Steps to Reproduce:
1.Opened a file called demo.js.
2.Disconnected the network and made some changes to demo.js. At this point, the file couldn't be saved because the network was disconnected, which is expected.
3.Reconnected the network and noticed that the unsaved changes in demo.js couldn't be saved anymore.
After multiple attempts, it seems that this is because the time taken to reconnect after the network was disconnected was less than 5 seconds. As a result, the backend continued to reuse the old socket, which caused the inability to save the file.
Additional Information:
The text was updated successfully, but these errors were encountered: