-
Notifications
You must be signed in to change notification settings - Fork 38.2k
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugconfirmedIssue has been confirmed by VS Code Team memberIssue has been confirmed by VS Code Team memberelectronIssues and items related to ElectronIssues and items related to Electroninsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersmacosIssues with VS Code on MAC/OS XIssues with VS Code on MAC/OS XupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeededVerification succeeded
Milestone
Description
Type: Bug
If you have a NODE_EXTRA_CA_CERTS environment variable in place, then when launching VS Code from a command line, a warning message is displayed:
[0201/100616.044843:ERROR:node_main.cc(135)] Node.js environment variables are disabled because this process is invoked by other apps.
The extra certificates are required for our environment to support proxy/VPN connectivity. Ideally these values would be used in VS Code; but, at the very least, the warning shouldn't show up on the console during launch.
VS Code version: Code 1.86.0 (0504748, 2024-01-31T10:29:11.933Z)
OS version: Darwin arm64 23.3.0
Modes:
System Info
| Item | Value |
|---|---|
| CPUs | Apple M1 Max (10 x 24) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | 6, 4, 3 |
| Memory (System) | 32.00GB (3.50GB free) |
| Process Argv | --disable-extensions --crash-reporter-id 1021646e-a5d4-4a1c-bf5d-3f1296f9cf93 |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
0bi6i642:30951795
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
accentitlementst:30887150
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
dsvsc019b:30953937
3ef8e399:30949928
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugconfirmedIssue has been confirmed by VS Code Team memberIssue has been confirmed by VS Code Team memberelectronIssues and items related to ElectronIssues and items related to Electroninsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersmacosIssues with VS Code on MAC/OS XIssues with VS Code on MAC/OS XupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeededVerification succeeded