Gauge language runner / load problem #106428
Description
- VSCode Version: 1.49.0
- OS Version: Windows 10
Steps to Reproduce:
- Have long complicated spec/step_implemetation/test_libraries
- Start VS code with spec in window.
Does this issue occur when all extensions are disabled?: No, because it does not try to load gauge then
Receive errors:
Current gauge language runner is not compatible with gauge LSP. Some of the editing feature will not work as expected
unable to connect to runner : Timed out connecting to python
had no problems with Gauge this morning, but as soon as update hit for VS Code, the errors started occurring. This happened in the past, and was debugger related. Tried to update via pip-check and updates. was not related to those. I feel its related to timing on startup. Will continue to search for a solution as this is critical to our coding.
note: output for gauge shows:
--> request #1: gauge/getRunnerLanguage: null
<-- request #0: client/registerCapability: {"registrations":[{"id":"gauge-fileWatcher","method":"workspace/didChangeWatchedFiles","registerOptions":{"watchers":[{"globPattern":"c:/CompanyName/controls_test/**/*{.spec,.md,.cpt}","kind":5}]}}]}
<-- result #1: gauge/getRunnerLanguage: ""
--> result #0: client/registerCapability: null
<-- notif: window/logMessage: {"type":1,"message":"notif #0: initialized: current runner is not compatible with gauge LSP"}
[Error - 5:07:34 PM] notif #0: initialized: current runner is not compatible with gauge LSP
also note:
Debug is no longer there