Restart task fails if task already completed

We have writ Issue Type: <b>Bug</b> Build tasks are often quite long (especially when building for embedded systems) and it's common for them to throw up intermediate errors before completion. In this case a typical pattern is ... - start build task - spot error report in early build output - edit offending file - run build task again At this stage if the original build task is still running a dialog is presented giving the option to terminate/restart. If 'restart' is chosen but the task completed while the dialog was being presented, you get another error saying the task couldn't be terminated. (Although this may be technically correct, failing to terminate because the task has already closed doesn't really seem like something worth reporting.) Really the behaviour I want is for CTRL-B to just terminate any current build tasks and start a new one unconditionally. Perhaps there is a way to customise preferences to get this behaviour? (Goes off to explore options...) VS Code version: Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:20:54.427Z) OS version: Windows_NT x64 10.0.16299 <details> <summary>System Info</summary> |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz (8 x 2806)| |GPU Status|2d_canvas: enabled<br>checker_imaging: disabled_off<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>native_gpu_memory_buffers: disabled_software<br>rasterization: unavailable_off<br>surface_synchronization: enabled_on<br>video_decode: enabled<br>webgl: enabled<br>webgl2: enabled| |Memory (System)|5.99GB (1.01GB free)| |Process Argv|--folder-uri file:///j%3A/esp| |Screen Reader|no| |VM|0%| </details><details><summary>Extensions (17)</summary> Extension|Author (truncated)|Version ---|---|--- Bookmarks|ale|10.2.2 numbered-bookmarks|ale|6.1.0 comments|Ale|1.0.4 vscode-markdownlint|Dav|0.24.0 vscode-instant-markdown|dba|1.4.3 g…