-
Notifications
You must be signed in to change notification settings - Fork 294
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
fix: tag experimental settings with new system #16116
Conversation
@@ -1802,16 +1803,16 @@ | |||
"type": "boolean", | |||
"default": false, | |||
"description": "Experimental feature to enable execution analysis in notebooks", | |||
"scope": "application" | |||
"scope": "application", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are the settings executionAnalysis.enabled
and interactive.notebookRepl
using different tags.
One has onExp and other doesn't have it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
onExP means the setting could be assigned to an A/B experiment.
If that's not the intent behind the setting, I could remove that tag from the setting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there an A/B experiment for (or planned for) executionAnalysis.enabled
? that's what that tag is for.
Eventually we'll get an experiment for the notebook REPL.
I'm retagging some Jupyter extension settings as part of the experimental -> onExP rename where: