Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker view keeps loading without any notification if there is no Docker Desktop installed #3132

Closed
v-ruizh opened this issue Aug 12, 2021 · 6 comments · Fixed by #3153
Closed

Comments

@v-ruizh
Copy link

v-ruizh commented Aug 12, 2021

OS: Win 10
Build Version: 20210809.1
Regression: Previous Release

Repro Steps:

  1. Make sure there is no Docker Desktop on the machine.
  2. Install the Docker extension in VS Code.
  3. Open the Docker view.
  4. Check whether a notification pops up to remind user to install Docker Desktop.

Expect:
A notification pops up to remind user to install Docker Desktop.
expect

Actual:
Docker view keeps loading without any notification.
testactual

More Info:

  1. This notification pops up after expanding the Networks/Volumes/Contexts view.
  2. This issue does not reproduce on the previous released Docker extension 1.15.0.
@v-ruizh v-ruizh added the AT-CTI label Aug 12, 2021
@karolz-ms
Copy link
Contributor

Side-effect of #3109 ?

@bwateratmsft
Copy link
Collaborator

bwateratmsft commented Aug 12, 2021 via email

@bwateratmsft
Copy link
Collaborator

I'm able to reproduce. I think what is happening is the containers and images views start their first refresh call which awaits on ContextLoadingClient--which will not forward the call until it observes the onContextChanged event from the context manager. However, the event is only fired if no exception is thrown.

@karolz-ms I think maybe we should have two separate events in DockerContextManager, leave onContextChanged as it is now, but add one for onLoadingFinished specifically for ContextLoadingClient. This one would fire regardless of success/failure of context loading, i.e. by being in the finally. What do you think?

@bwateratmsft bwateratmsft self-assigned this Aug 12, 2021
@karolz-ms
Copy link
Contributor

@bwateratmsft yes, that makes sense to me.

@bwateratmsft
Copy link
Collaborator

Discussed offline and we'll fix this in 1.17.0.

@bwateratmsft
Copy link
Collaborator

The fix for this has been released in Docker extension 1.17.0.

@vscodebot vscodebot bot locked and limited conversation to collaborators Oct 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants