Skip to content

Connect to raw kernel with command line args instead of connection file #11894

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

Conversation

IanMatthewHuff
Copy link
Member

For #11883

  • Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
  • Title summarizes what is changing.
  • Has a news entry file (remember to thank yourself!).
  • Appropriate comments and documentation strings in the code.
  • Has sufficient logging.
  • Has telemetry for enhancements.
  • Unit tests & system/integration tests are added/updated.
  • Test plan is updated as appropriate.
  • package-lock.json has been regenerated by running npm install (if dependencies have changed).
  • The wiki is updated with any design decisions/details.

@@ -271,7 +271,7 @@
],
"env": {
// Remove `X` prefix to test with real browser to host DS ui (for DS functional tests).
"xVSC_PYTHON_DS_UI_BROWSER": "1",
"XVSC_PYTHON_DS_UI_BROWSER": "1",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That little x was bugging me 😆

// Update the args in the kernelspec to include the conenction file.
// Instead of having to use a connection file update our local copy of the kernelspec to launch
// directly with command line arguments
private updateConnectionArgs() {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought briefly about where to handle this and I believe this is the right spot.

  1. We already make a deep copy of the kernelspec in KernelProcess so that we can mess with it, but not change the original spec
  2. Same location we were previously creating and inserting the connection file info.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested on windows as well. Not fully sure if this fixes the nightly test runs (as those issues don't seem to repro doing real python tests locally) so I'll queue up a run for that. I would expect this to fix the nightly test issues but even if there was another issue there this new method seems like a solid improvement, no messing around with creating and removing files.

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

Copy link

@rchiodo rchiodo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@rchiodo
Copy link

rchiodo commented May 19, 2020

Hey did you try a nightly run? Can't seem to find it. Was curious if it worked or not.

@IanMatthewHuff
Copy link
Member Author

@rchiodo Just queued it up. Just didn't do that until after lunch. I'm going to submit regardless as I think it's a good change anyways. Fingers crossed that it fixes the windows flakes as well.

@IanMatthewHuff IanMatthewHuff merged commit 28ded73 into microsoft:master May 19, 2020
@IanMatthewHuff IanMatthewHuff deleted the dev/ianhu/noConnectionFileLaunch branch May 19, 2020 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants