Skip to content

Log ComSpec and add diagnostic to validate it #16692

@karthiknadig

Description

@karthiknadig

We see this often where ComSpec env variable is some how set to invalid path. We should detect this and log. This happens way too often.

Essentially the ENOENT (-4058) error with -c " " error usually means that Node exec tried to get default shell on Windows using ComSpec and since ComSpec was wrong it was failing while trying to shell execute python commands.

Originally posted by @karthiknadig in #16684 (comment)

Metadata

Metadata

Assignees

Labels

area-editor-*User-facing catch-alldebtCovers everything internal: CI, testing, refactoring of the codebase, etc.needs PRReady to be worked on

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions