When the vscode extension tries to restart `qmlls` with new parameters, `qmlls` sends the `[ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed` error and the language client shows an error message to the user. Interestingly, this problem does not occur when the extension restarts `qmlls` after startup. It only happens on startup. When I reverted I6f164e640234af15a437e10d404ae62c40286099, the error message the language client shows to the user has changed from `Connection to server got closed. Server will not be restarted.` to `Client qmlls: connection to server is erroring. Cannot call write after a stream was destroyed` but `[ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed` persists in the log.

I attached a verbose qml log. I can also share more information if needed.

qmlls_verbose.log