You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating to VSCode March 2019 (stable, tested on macOS and on Windows), environment variables used in task definitions are no longer resolved, they are emptystring instead.
This renders all tasks unuseable that in any way rely on environment variables directly (e.g. starting a tomcat via ${env:CATALINA_HOME}/bin/startup.sh).
VS Code version: Code 1.33.0 (0dd516d, 2019-04-04T15:11:32.076Z)
OS version: Darwin x64 18.5.0
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12 x 2600)
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.
Issue Type: Bug
After updating to VSCode March 2019 (stable, tested on macOS and on Windows), environment variables used in task definitions are no longer resolved, they are emptystring instead.
Consider the following tasks.json:
expected:
/Users/me == /Users/me
actual:
/Users/me ==
This renders all tasks unuseable that in any way rely on environment variables directly (e.g. starting a tomcat via
${env:CATALINA_HOME}/bin/startup.sh
).VS Code version: Code 1.33.0 (0dd516d, 2019-04-04T15:11:32.076Z)
OS version: Darwin x64 18.5.0
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Extensions (11)
(2 theme extensions excluded)
The text was updated successfully, but these errors were encountered: