The title is an error that pops up that ends up breaking Rojo indefinitely, with "strenuous" workarounds.
Reproduction Steps
I am able to replicate this error by spinning the studio extension up before the Rojo server has started via Ctrl+P > Rojo: Start server with last used project file with the error being rather persistent even when re-opening Visual Studio Code, reinstalling the extension and/or reimporting my place from a .rbxlx file via rbxlx-to-rojo.
Note
There is uncertainty as to whether being in Zen Mode would cause any problems as there is a setting that mutes notifications.
Conclusion
An obvious one would be to wait until the notification appears then start the server like any individual with a normal amount of patience, however, I feel as if there could be a more elegant way to notify the developer of their impatience; to mitigate such an error from seemingly breaking the extension; either/both.
Issue
The title is an error that pops up that ends up breaking Rojo indefinitely, with "strenuous" workarounds.
Reproduction Steps
I am able to replicate this error by spinning the studio extension up before the Rojo server has started via
Ctrl+P > Rojo: Start server with last used project filewith the error being rather persistent even when re-opening Visual Studio Code, reinstalling the extension and/or reimporting my place from a.rbxlxfile via rbxlx-to-rojo.Note
There is uncertainty as to whether being in Zen Mode would cause any problems as there is a setting that mutes notifications.
Conclusion
An obvious one would be to wait until the notification appears then start the server like any individual with a normal amount of patience, however, I feel as if there could be a more elegant way to notify the developer of their impatience; to mitigate such an error from seemingly breaking the extension; either/both.