-
Notifications
You must be signed in to change notification settings - Fork 42
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
1.7.0 breaks remote module execution #108
Comments
@alfredodeza thanks a lot for the detailed diagnosis. I'm fine with removing the optimization, I'm sure the gains are negligible (@joaoe do you agree)? @alfredodeza would you like to open a PR? I would love to merge it and make a new release. 👍 |
I am working on a PR. Thanks @nicoddemus for the quick action on this issue |
Yes, sure. It's really not worthwhile to add any complexity to that part of the code. Might I also recommend that you add a test that ensure that execnet works when the source is not available remotely ? That would have saved a bug. :) But replace the if/else with |
this was closed by #109 |
The latest release (1.7.0) which includes the changes in this commit in particular: 544bcc8 is causing remote module execution to not work at all.
In gateway.py, this block:
Makes
source
always aNone
which is not correct. If/when commenting thissource = None
condition, a serialize error is raised:I don't know what can I suggest here other than removing the optimization (as explained here 544bcc8#r310201906) since going back to 1.6 or anything previous to that commit, allows us to have a working application using remote modules
The text was updated successfully, but these errors were encountered: