-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Load module on remote workers from master (v2) #21695
Conversation
Commit messages should really be more descriptive |
Can this fix be backported to v0.5? (as per request for superseded PR) |
I think this should be good to go now. |
I think this should be eligible for backporting. Unfortunately, 0.5.2 was just released, but we can do a 0.5.3 release in a month or so. |
Needed on 0.6 as well I think? |
Yes sorry, this is needed on 0.5, 0.6 and 0.7. |
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.
Looks good to me. Please squash the commits so that it is bisect friendly.
Ha! Looks like my squash worked! |
@tkelman Looks like this was missed for v0.5.3. Will we get this in a v0.5.4? |
Is there any update on when 0.5.3 might be released? |
Any update on backport to v0.5? |
How critical is having this on 0.5? Most of the ecosystem is moving to 0.6-only now, I wasn't thinking another 0.5.x point release would be necessary. |
Well I guess nothing is really critical. For my main project, I'm still using v0.4.5, which is the last version where remote code loading worked for me. I wanted to upgrade to v0.5 as an intermediate step, before upgrading to v0.6. I suppose I can upgrade to v0.6 directly, but was holding out in anticipation of a 0.5.x release that includes the fix for this issue. So I guess I can't really justify asking for another 0.5.x release just for this issue. |
Fix Issue #19960
Replace PR #21647
Is it OK to suggest some more labels?
backport pending 0.5
backport pending 0.6
bugfix