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

Got both the walkthrough and Get Started page #3235

Closed
digitarald opened this issue Sep 24, 2021 · 4 comments Β· Fixed by #3248
Closed

Got both the walkthrough and Get Started page #3235

digitarald opened this issue Sep 24, 2021 · 4 comments Β· Fixed by #3248

Comments

@digitarald
Copy link

Tested on Insiders:

  • Installed Docker β†’ Walkthrough opened
  • Opened Docker sidebar

πŸ› Docker - Getting Started opens

@digitarald digitarald added the bug label Sep 24, 2021
@bwateratmsft bwateratmsft added this to the 1.18.0 milestone Sep 24, 2021
@bwateratmsft bwateratmsft self-assigned this Sep 24, 2021
@bwateratmsft
Copy link
Contributor

Looking into why VSCode and Docker are coming up with different values for the experiment...

@bwateratmsft
Copy link
Contributor

I have a theory--the Docker extension will mark itself as "Team" population group if it's being debugged (i.e., us mainly), "Insiders" if "alpha" is in the version number, and "Public" otherwise.

On the other hand, VSCode Insiders will report itself as Insiders.

What may be happening is @digitarald is in the control group (50%) for "Public" (what the Docker extension sees), but in the treatment group (100%) for Insiders (what VSCode sees).

@bwateratmsft
Copy link
Contributor

I shut down the experiment for the Insiders population group, so this should no longer happen--it will never show the walkthrough on Insiders, and should have 50/50 to show the start page on first activation.

It's sort of moot because most likely the start page will be removed entirely in 1.18.0.

@bwateratmsft
Copy link
Contributor

This fix is now released in Docker extension version 1.18.0.

@microsoft microsoft locked and limited conversation to collaborators Nov 23, 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.

2 participants