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
Describe the bug
Starting up erlang_ls in shell mode with els_fake_stdio as the IO device used by the els_client causes forever loop.
To Reproduce
Start the erlang_ls in shell mode with els_fake_stdio and els_client (rebar3 shell).
Expected behavior
Logging should not cause more logging.
Actual behavior
The 'Started erlang_ls server' log message was issued. This caused a window/logMessage from the server to the client (in our case it is the els_client). The do_handle_message/3 function discarded the message and issued a log message. And the forever loop is now in action. Take a look at the first couple line of the log:
Describe the bug
Starting up erlang_ls in shell mode with
els_fake_stdio
as the IO device used by theels_client
causes forever loop.To Reproduce
Start the erlang_ls in shell mode with
els_fake_stdio
andels_client
(rebar3 shell
).Expected behavior
Logging should not cause more logging.
Actual behavior
The 'Started erlang_ls server' log message was issued. This caused a window/logMessage from the server to the client (in our case it is the
els_client
). Thedo_handle_message/3
function discarded the message and issued a log message. And the forever loop is now in action. Take a look at the first couple line of the log:Pretty soon the escaping in the log file goes overdrive. The log file is 71 lines and 15MB size.
Context
erlang_ls
version (tag/sha): 1.1.0The text was updated successfully, but these errors were encountered: