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

PR: Tunnel comm port to make all features that depend on comms work for remote kernels #14447

Merged
merged 2 commits into from
Feb 14, 2021

Conversation

impact27
Copy link
Contributor

Description of Changes

  • Wrote at least one-line docstrings (for any new functions)
  • Added unit test(s) covering the changes (if testable)
  • Included a screenshot or animation (if affecting the UI, see Licecap)

Issue(s) Resolved

Fixes #11538

Affirmation

By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:

@ccordoba12 ccordoba12 changed the title PR: tunnel comm port PR: Tunnel comm port to make all features that depend on comms work for remote kernels Dec 17, 2020
@ccordoba12 ccordoba12 changed the base branch from master to 4.x December 17, 2020 15:18
@ccordoba12 ccordoba12 modified the milestones: v4.2.2, v4.2.1 Dec 17, 2020
Copy link
Member

@ccordoba12 ccordoba12 left a comment

Choose a reason for hiding this comment

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

I finally had the chance to test this locally and it's working as expected.

This is a terrific improvement!! Thanks a lot @impact27 for your help with it!

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.

Variable explorer doesn't show variables on remote kernel
2 participants