Add canary test for internal Jupyter APIs - #3696
Draft
Andrew Casey (amcasey) wants to merge 3 commits into
Draft
Andrew Casey (amcasey) wants to merge 3 commits into
Andrew Casey (amcasey) wants to merge 3 commits into
Conversation
We call a few internal Jupyter APIs in order to be able to manipulate notebook python environments. Add a new scheduled test (not part of CI) that will let us know if those APIs are removed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The two commits in this PR show two different approaches. The first minimally confirms that the APIs are accessible. The second actually uses them.