Skip to content
New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

Update to 2.0.7 #4130

Closed
CharnaceRegis opened this issue Mar 20, 2024 · 30 comments
Closed

Update to 2.0.7 #4130

CharnaceRegis opened this issue Mar 20, 2024 · 30 comments
Labels
upstream

Comments

@CharnaceRegis
Copy link

CharnaceRegis commented Mar 20, 2024 •
edited
Loading

Since 2.0.7,

[Error - 17:06:43] Client Vue: connection to server is erroring.
write EPIPE
[Error - 17:06:43] Client Vue: connection to server is erroring.
write EPIPE
Shutting down server.
[Error - 17:06:43] Client Vue: connection to server is erroring.
write EPIPE
Shutting down server.
[Error - 17:06:43] Client Vue: connection to server is erroring.
write EPIPE
Shutting down server.
[Error - 17:06:43] Client Vue: connection to server is erroring.
write EPIPE
Shutting down server.
[Error - 17:06:43] Server process exited with signal SIGBUS.
[Error - 17:06:43] Connection to server got closed. Server will not be restarted.

Apple M1 - 16Go
I've downgraded to 2.0.6
@dcartwright07
Copy link

After upgrading to 2.0.7, I also got errors in VSCode output console.

[Error - 12:08:36 PM] Server process exited with signal SIGBUS.
[Info  - 12:08:36 PM] Connection to server got closed. Server will restart.
true
[Error - 12:08:37 PM] Server process exited with signal SIGBUS.
[Info  - 12:08:37 PM] Connection to server got closed. Server will restart.
true
[Error - 12:08:37 PM] Server process exited with signal SIGBUS.
[Info  - 12:08:37 PM] Connection to server got closed. Server will restart.
true
[Error - 12:08:38 PM] Server process exited with signal SIGBUS.
[Info  - 12:08:38 PM] Connection to server got closed. Server will restart.
true
[Error - 12:08:39 PM] Server process exited with signal SIGBUS.
[Error - 12:08:39 PM] The Vue server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.

I also downgraded to 2.0.6 and the extension stopped crashing.

@johnsoncodehk
Copy link
Member

Will the problem still occur if you enable vue.server.hybridMode in VSCode settings?

@dcartwright07 Since the error message is different, I'm not sure if you have the same issue.

If anyone can help me debug this issue via remote desktop, please contact me in the Vue discord server.

@claylevering
Copy link

Will the problem still occur if you enable vue.server.hybridMode in VSCode settings?

@dcartwright07 Since the error message is different, I'm not sure if you have the same issue.

If anyone can help me debug this issue via remote desktop, please contact me in the Vue discord server.

Pinged you in paid and trying to find you in discord but unsure where to find you in Vue Land

@dharnil
Copy link

dharnil commented Mar 21, 2024

What did you do to Diagnose this issue?

@madcodelife
Copy link

After upgrading to 2.0.7, I also got errors in VSCode output console.

[Error - 12:08:36 PM] Server process exited with signal SIGBUS.
[Info  - 12:08:36 PM] Connection to server got closed. Server will restart.
true
[Error - 12:08:37 PM] Server process exited with signal SIGBUS.
[Info  - 12:08:37 PM] Connection to server got closed. Server will restart.
true
[Error - 12:08:37 PM] Server process exited with signal SIGBUS.
[Info  - 12:08:37 PM] Connection to server got closed. Server will restart.
true
[Error - 12:08:38 PM] Server process exited with signal SIGBUS.
[Info  - 12:08:38 PM] Connection to server got closed. Server will restart.
true
[Error - 12:08:39 PM] Server process exited with signal SIGBUS.
[Error - 12:08:39 PM] The Vue server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.

I also downgraded to 2.0.6 and the extension stopped crashing.

I got same issue.

@drylint
Copy link

drylint commented Mar 21, 2024

Will the problem still occur if you enable vue.server.hybridMode in VSCode settings?

@dcartwright07 Since the error message is different, I'm not sure if you have the same issue.

If anyone can help me debug this issue via remote desktop, please contact me in the Vue discord server.

It still occur after enabled vue.server.hybridMode in VSCode settings.

@drylint
Copy link

drylint commented Mar 21, 2024

When enabled vue.server.hybridMode, It reports another error repeatedly. @johnsoncodehk

service 2 crashed on file:///Users/......./***.vue?virtualCodeId=script_ts No service provide typescript/languageService

......repeatedly

@johnsoncodehk
Copy link
Member

What did you do to Diagnose this issue?

I currently have no clue as to how this problem occurs, I need to identify where the error is being thrown first.

If you want to try debugging: https://github.com/vuejs/language-tools#contribution-guide

When enabled vue.server.hybridMode, It reports another error repeatedly. @johnsoncodehk

service 2 crashed on file:///Users/......./***.vue?virtualCodeId=script_ts No service provide typescript/languageService

......repeatedly

You can ignore it, it's just harmless logs.

@dcartwright07
Copy link

dcartwright07 commented Mar 21, 2024 •
edited
Loading

@johnsoncodehk When vue.server.hybridMode is enabled, the extension does not crash. I am no longer getting the same errors in the output console. I do get the error @drylint reported but it doesn't seem to be causing any issues.

I am not sure if this helps but I did get the same error message as @CharnaceRegis. The error messages I posted earlier was after I click to view the error log.

Screenshot 2024-03-20 at 10 15 46 PM

@juzser
Copy link

juzser commented Mar 21, 2024 •
edited
Loading

I get the same issue. Enable or disable the hybrid mode the issue is still occur.

Screenshot 2024-03-21 at 15 13 23

@Shyam-Chen
Copy link

Fix this issue using VS Code v1.88.0.

@CharnaceRegis
Copy link
Author

CharnaceRegis commented Mar 21, 2024 •
edited
Loading

I agree with that. Insiders version of VS Code. Unfortunately, l don't have any code completion

@johnsoncodehk
Copy link
Member

Possibly due to the reintroduction of the full language server in #4119, the issue mentioned in #3962 has spread to the Vue language server in some form, I will update the version required by the extension when VSCode 1.88 is released.

@filipbekic01
Copy link

It's crazy how annoying this bug can be.

@Mert75
Copy link

Mert75 commented Mar 21, 2024

It's crazy how annoying this bug can be.

you can still rollback to the previous release and have it working again

@juzser
Copy link

juzser commented Mar 21, 2024

I had to rollback to 1.8.27. But the problem is the package @vue/language-plugin-pug also had to rollback.
So maybe there is miss-synced of package.json between contributors.

@MichaelGitArt
Copy link

hybridMode

It's okay with hybridMode.

Or almost okay. The server runs okay, but there are some service crashes. But it's okay with it
image

@ningyf
Copy link

ningyf commented Mar 22, 2024

The JS/TS language service immediately crashed 5 times. The service will not be restarted. This may be caused by a plugin contributed by one of these extensions: Vue.volar. Please try disabling these extensions before filing an issue against VS Code.

It aways cause this error since 2.x. I downgrade to v1 to fix this issue.

The vscode output logs:
2024-03-22 10:34:35.207 [info] Starting TS Server
2024-03-22 10:34:35.207 [info] Using tsserver from: /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
2024-03-22 10:34:35.207 [info] Forking...
2024-03-22 10:34:35.207 [info] Starting...
2024-03-22 10:34:35.207 [info] Forking...
2024-03-22 10:34:35.207 [info] Starting...
2024-03-22 10:34:37.902 [error] TSServer exited. Code: null. Signal: SIGBUS

@Lakphy
Copy link

Lakphy commented Mar 22, 2024

I got the same issue. Do I have to downgrade the plugin or upgrade vscode to solve it? I have not received the vscode 1.88 update yet.

[Error - 16:51:28] Server process exited with signal SIGBUS.
[Info  - 16:51:28] Connection to server got closed. Server will restart.
true
[Error - 16:51:30] Server process exited with signal SIGBUS.
[Info  - 16:51:30] Connection to server got closed. Server will restart.
true
[Error - 16:51:32] Server process exited with signal SIGBUS.
[Info  - 16:51:32] Connection to server got closed. Server will restart.
true
[Error - 16:51:33] Server process exited with signal SIGBUS.
[Info  - 16:51:33] Connection to server got closed. Server will restart.
true
[Error - 16:51:34] Server process exited with signal SIGBUS.
[Error - 16:51:34] The Vue server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.

@OlaAlsaker
Copy link

Using VS Code Insiders fixed the issue for me.

@Nagell
Copy link

Nagell commented Mar 22, 2024

Here similar situation. Directly after starting VSC and opening a Vue file.

log preview - click to open 
[Error - 10:37:39 AM] Server process exited with signal SIGBUS.
[Info  - 10:37:39 AM] Connection to server got closed. Server will restart.
true
[Error - 10:37:39 AM] Server process exited with signal SIGBUS.
[Info  - 10:37:39 AM] Connection to server got closed. Server will restart.
true
[Error - 10:37:40 AM] Server process exited with signal SIGBUS.
[Info  - 10:37:40 AM] Connection to server got closed. Server will restart.
true
[Error - 10:37:41 AM] Server process exited with signal SIGBUS.
[Info  - 10:37:41 AM] Connection to server got closed. Server will restart.
true
[Error - 10:37:42 AM] Server process exited with signal SIGBUS.
[Error - 10:37:42 AM] The Vue server crashed 5 times in the last 3 minutes.

Setup:

  • MacOS: 14.4
  • VSC: v1.87.2
    • Version: 1.87.2 (Universal)
    • Commit: 863d2581ecda6849923a2118d93a088b0745d9d6
    • Date: 2024-03-08T15:21:31.043Z
    • Electron: 27.3.2
    • ElectronBuildId: 26836302
    • Chromium: 118.0.5993.159
    • Node.js: 18.17.1
    • V8: 11.8.172.18-electron.0
    • OS: Darwin arm64 23.4.0
  • freshly created Profile with only Two plugins:
    • ESLint: 2.4.4
    • Vue-Official: 2.0.7

@laurens94 laurens94 mentioned this issue Mar 22, 2024
Closed
@zernonia zernonia mentioned this issue Mar 25, 2024
Closed
@ilyakamens
Copy link

Also happening to me.

@Shyam-Chen
Copy link

microsoft/vscode#208302

VS Code v1.88 scheduled for release on 4/4.

@mrleblanc101
Copy link

mrleblanc101 commented Mar 29, 2024 •
edited
Loading

Shouldn't this be reverted in a 2.0.8. Then the next 2.0.9 version could bump the min required VS Code version to 1.88 so that both user of 1.87 and 1.88 would have a working plugin instead of forcing everyone to pin the version manually until they update ?

@johnsoncodehk johnsoncodehk mentioned this issue Mar 29, 2024
Closed
@LcpMarvel
Copy link 

rejected promise not handled within 1 second: Error: Request volar/client/tsconfig failed with message: Invalid file name
extensionHostProcess.js:144
stack trace: Error: Request volar/client/tsconfig failed with message: Invalid file name
    at handleResponse (/Volumes/lcp/git_repos/language-tools/node_modules/.pnpm/vscode-jsonrpc@8.2.0/node_modules/vscode-jsonrpc/lib/common/connection.js:565:48)
    at handleMessage (/Volumes/lcp/git_repos/language-tools/node_modules/.pnpm/vscode-jsonrpc@8.2.0/node_modules/vscode-jsonrpc/lib/common/connection.js:345:13)
    at processMessageQueue (/Volumes/lcp/git_repos/language-tools/node_modules/.pnpm/vscode-jsonrpc@8.2.0/node_modules/vscode-jsonrpc/lib/common/connection.js:362:17)
    at Immediate.<anonymous> (/Volumes/lcp/git_repos/language-tools/node_modules/.pnpm/vscode-jsonrpc@8.2.0/node_modules/vscode-jsonrpc/lib/common/connection.js:334:13)
    at processImmediate (node:internal/timers:476:21)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)

@khgs2411
Copy link

2.0.8 has the same problem.
If vscode 1.88 fixes this issue, then this release schedule for the extension is utterly baffling...why release a broken product?

@johnsoncodehk johnsoncodehk mentioned this issue Mar 31, 2024
Closed
@ipid
Copy link

ipid commented Apr 1, 2024 •
edited
Loading

Same here on MacBook Pro 2023, M2 Pro, macOS 14.2.1

[Error - 12:09:34] Server process exited with signal SIGBUS.
[Info  - 12:09:34] Connection to server got closed. Server will restart.
true
[Error - 12:09:35] Server process exited with signal SIGBUS.
[Info  - 12:09:35] Connection to server got closed. Server will restart.
true
[Error - 12:09:36] Server process exited with signal SIGBUS.
[Info  - 12:09:36] Connection to server got closed. Server will restart.
true
[Error - 12:09:37] Server process exited with signal SIGBUS.
[Info  - 12:09:37] Connection to server got closed. Server will restart.
true
[Error - 12:09:38] Server process exited with signal SIGBUS.
[Error - 12:09:38] The Vue server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.

@so1ve so1ve mentioned this issue Apr 2, 2024
Closed
@ggaabe ggaabe mentioned this issue Apr 2, 2024
Open
@johnsoncodehk
Copy link
Member

2.0.8 has the same problem. If vscode 1.88 fixes this issue, then this release schedule for the extension is utterly baffling...why release a broken product?

This is an unpredictable error that occurs in random projects and environments. It was not occur in self-test and 3 months alpha test.

To be honest, it's not fair to blame the extension for Node bugs. We could not anticipate that the Node version of the stable VSCode bundled would be unstable.

Closed since VSCode 1.88 has been released.

@masawik
Copy link

masawik commented Apr 11, 2024

installing an earlier version (2.0.6) fixed it

image

@LcpMarvel
Copy link

installing an earlier version (2.0.6) fixed it

image

Download the latest https://code.visualstudio.com/.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
upstream
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests