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.

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

code command's wait (-w, --wait) is crashing since ~1.95.2 #233409

Closed
itsthejb opened this issue Nov 8, 2024 · 5 comments
Closed

code command's wait (-w, --wait) is crashing since ~1.95.2 #233409

itsthejb opened this issue Nov 8, 2024 · 5 comments
Assignees
Labels
confirmation-pending info-needed Issue requires more information from poster

Comments

@itsthejb
Copy link

itsthejb commented Nov 8, 2024

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: 1.95.2 e8653663e8840adaf45af01eab5c627a5af81807 arm64
  • OS Version: macOS 15.1 (24B83)

Steps to Reproduce:

The command-line code's wait flag (-w --wait) is failing since around 1.95.2

  1. touch test.txt && code -w test.txt
  2. Crashes with:
node:internal/errors:541
      throw error;
      ^

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received undefined
    at Module.access (node:fs:229:10)
    at t.access (node:electron/js2c/node_init:2:7532)
    at Timeout._onTimeout (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/cli.js:29:95356)
    at listOnTimeout (node:internal/timers:581:17)
    at process.processTimers (node:internal/timers:519:7) {
  code: 'ERR_INVALID_ARG_TYPE'
}

Node.js v20.18.0
@vs-code-engineering vs-code-engineering bot added the stale Issues that have not been triaged in an appropriate amount of time label Nov 19, 2024
@dbaeumer dbaeumer assigned bpasero and unassigned dbaeumer and hediet Nov 20, 2024
@dbaeumer dbaeumer removed triage-needed stale Issues that have not been triaged in an appropriate amount of time labels Nov 20, 2024
@bpasero
Copy link
Member

bpasero commented Nov 20, 2024

I cannot reproduce, nor was it reported by other users.

@bpasero bpasero added info-needed Issue requires more information from poster confirmation-pending labels Nov 20, 2024
@itsthejb
Copy link
Author

@bpasero did you run the command from within a VSCode terminal? That's where the issue occurs. Does not happen when running from a separate terminal. I'm also using zsh, but I has a quick test with bash and this made no difference

@itsthejb
Copy link
Author

itsthejb commented Nov 24, 2024

@sansmoraxz can you confirm that you also have this issue please?

@sansmoraxz
Copy link

Had it previously. But for me it went away after I deleted .vscode-server and reinstalled everything.

@itsthejb
Copy link
Author

itsthejb commented Nov 24, 2024

@sansmoraxz Thanks for the input. I can confirm that moving aside ~/.vscode and restarting also fixes the issue for me. So it would seem this is affected by some stale data in there. Which certainly is odd...

Edit: most likely it's caused by an extension...

@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Jan 8, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
confirmation-pending info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

5 participants