Closed aharpervc closed 7 years ago
Pretty sure this is all that is needed?
@aharpervc Executor.runInTerminal() is an async function, so this change will not take effect.
I see. What's the fix?
There need more code refactoring without using runInTerminal
. One option is using child_process.execSync
API. One thing I am curious is that why you would like disable the auto-refresh. Is there any side effect of it? With the auto-refresh, we don't need to refresh container after any operation is done. 😄
I often keep "Docker for Win/Mac" turned off, so this creates problems with the cli tool can't talk to that service. Also I run quite a few instances of VS Code so that's a lot of notices and failing processes spawning all the time. Plus, I don't often change container state except when developing inside of VS Code, so it's not like the auto refresh would tell me about something I didn't just do manually. But since the UI doesn't refresh after taking a manual action with this extension, I have to manually click refresh every time.
Thanks @aharpervc for the detailed info. In that case, it seems that the only side effect of auto-refresh is that it will show error message for each VS Code instance. Therefore, a quick turnaround is to provide an option to allow user to let extension not show the error message. What's your thought about this?
Sure, that would help. You'd also have processes needlessly running and dying in the background unceasingly, but that's probably not that big of a deal.
I have no idea how notifications work, so go for it.
Fixes #12