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

Error notification: CustomEditor and NativeNotebook experiments cannot be turned on together #4105

Closed
aeschli opened this issue Dec 3, 2020 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@aeschli
Copy link

aeschli commented Dec 3, 2020

Testing codespaces scenario https://github.com/microsoft/vssaas-planning/issues/1593

image

Unclear to me as user what has caused this and what I need to do differently.

@karthiknadig karthiknadig transferred this issue from microsoft/vscode-python Dec 3, 2020
@DonJayamanne DonJayamanne self-assigned this Dec 3, 2020
@DonJayamanne
Copy link
Contributor

I think i know what's going on here.

  • In insiders NativeNotebook is always on in experiment.
  • Now assume user happens to fall into the CustomEditor experiment in VS Code Insiders.
    At this point, user is in both experiment groups.

Solution

  • Modify the inExperiment method to check if experiment argument == CustomEditor & if user already belongs to native notebook experiment, in such a case, just return false

@DonJayamanne DonJayamanne added the bug Issue identified by VS Code Team member as probable bug label Dec 3, 2020
@PaoloTCS
Copy link

PaoloTCS commented Dec 5, 2020

I have the identical message. Latest insiders edition of VSC.

@joyceerhl
Copy link
Contributor

Validated. I can't simulate control tower opting me into custom editor, but if I manually opt into native notebooks and custom editor experiments in VSCode Insiders, creating a new blank Jupyter notebook still opens into the native notebooks UI and I don't get a prompt.

@PaoloTCS we have a fix in for this. If the fix works as expected, it will be available in our next release, which will hopefully be in about 2 weeks' time. Thanks for letting us know 😊

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

4 participants