Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Version of ts-node causes error The Gauge server crashed 5 times in the last 3 minutes. The server will not be restarted. #885

Closed
mizuochi-hikaru opened this issue Sep 7, 2023 · 5 comments

Comments

@mizuochi-hikaru
Copy link

Describe the bug

I encountered #636 and #759, and I found below.

template-ts version gauge-vscode can start
0.9.0(latest) 🙅
0.8.0 🙅
0.7.0 🙆 OK!

I get diff between two templates, 0.8.0 and 0.7.0.

Common subdirectories: template-ts-0.0.7/.github and template-ts-0.0.8/.github
Common subdirectories: template-ts-0.0.7/env and template-ts-0.0.8/env
diff --color template-ts-0.0.7/metadata.json template-ts-0.0.8/metadata.json
4c4
<   "version": "0.0.7",
---
>   "version": "0.0.8",
diff --color template-ts-0.0.7/package.json template-ts-0.0.8/package.json
6c6
<     "ts-node": "^8.7.0",
---
>     "ts-node": "^10.4.0",
Common subdirectories: template-ts-0.0.7/specs and template-ts-0.0.8/specs
Common subdirectories: template-ts-0.0.7/tests and template-ts-0.0.8/tests

Therefore, as for title, I can say that version of ts-node causes error.
As a side note, version of gauge-ts and typescript has no effect on this error.

What command(s) did you run when you found the bug?

Open gauge-ts project in VSCode.

Output, stack trace or logs related to the bug

See #636 and #759.

Versions

Gauge (Output of gauge -v)

Gauge version: 1.5.4
Plugins
-------
dotnet (0.5.2)
html-report (4.2.0)
java (0.10.2)
js (3.0.1)
screenshot (0.1.0)
ts (0.1.0)

Node.js/Java/Python/.Net/Ruby version

$ node -v
v20.5.0

This is NOT used in VSCode.

Operating System information

Macbook Pro 2020 (Intel Chip)
Ventura 13.5.1

IDE information

Version: 1.81.1 (Universal)
Commit: 6c3e3dba23e8fadc360aed75ce363ba185c49794
Date: 2023-08-09T22:20:33.924Z
Electron: 22.3.18
ElectronBuildId: 22689846
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Darwin x64 22.6.0
@mizuochi-hikaru mizuochi-hikaru changed the title Version of ts-node causes error The Gauge server crashed 5 times in the last 3 minutes. The server will not be restarted." Version of ts-node causes error The Gauge server crashed 5 times in the last 3 minutes. The server will not be restarted. Sep 7, 2023
@bvobart
Copy link

bvobart commented Sep 14, 2023

Hi, thanks for doing that deep-dive dissection of this problem!! I was having the same issues as the ones you mentioned and had previously posted my findings there too.

I can indeed confirm that in the Gauge project that I'm working on, the VSCode extension starts working properly again after I downgrade ts-node to version 8.7.0.

bockstaller added a commit to bockstaller/getgauge-gauge that referenced this issue Oct 26, 2023
The getgauge/common upgrade solves the issue
where the gauge server crashes whenever a project is loaded
that uses the ts plugin.

The cause is described here getgauge#2419

This commit closes/permanently fixes issues like
getgauge/gauge-vscode#735
getgauge/gauge-vscode#636
getgauge/gauge-vscode#885

Signed-off-by: Lukas Bockstaller <lukas.bockstaller@posteo.de>
chadlwilson added a commit to getgauge/gauge that referenced this issue Oct 27, 2023
* Upgrade getgauge/common to solve ts issue

The getgauge/common upgrade solves the issue
where the gauge server crashes whenever a project is loaded
that uses the ts plugin.

The cause is described here #2419

This commit closes/permanently fixes issues like
getgauge/gauge-vscode#735
getgauge/gauge-vscode#636
getgauge/gauge-vscode#885

Signed-off-by: Lukas Bockstaller <lukas.bockstaller@posteo.de>

* Tidy Go modules

Signed-off-by: Chad Wilson <chadw@thoughtworks.com>

* Bump Gauge version

Signed-off-by: Chad Wilson <chadw@thoughtworks.com>

---------

Signed-off-by: Lukas Bockstaller <lukas.bockstaller@posteo.de>
Signed-off-by: Chad Wilson <chadw@thoughtworks.com>
Co-authored-by: Chad Wilson <chadw@thoughtworks.com>
@chadlwilson
Copy link
Contributor

Hopefully fixed by getgauge/gauge#2422 in Gauge 1.5.6 - we can re-open if it turns out not to be the case.

@mizuochi-hikaru
Copy link
Author

@chadlwilson
I updated and checked and it was OK!
Thank you for your support!

@chadlwilson
Copy link
Contributor

All credit and thanks goes to @bockstaller on this one; I'm just clicking some buttons to get the automation through :-)

@mizuochi-hikaru
Copy link
Author

@bockstaller
Sorry for the delay, but I read the investigation report(getgauge/gauge#2419). I was impressed by your handiwork!
Since I upgraded the version, my Gauge project has continued to work well.
Thank you so much for your help!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Development

No branches or pull requests

3 participants