-
Notifications
You must be signed in to change notification settings - Fork 618
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
fix(public-api): fix Job.call() using the wrong keyword (queue vs queue_name) when calling launch_add. #4625
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #4625 +/- ##
==========================================
+ Coverage 83.20% 83.23% +0.02%
==========================================
Files 279 279
Lines 34917 34917
==========================================
+ Hits 29054 29063 +9
+ Misses 5863 5854 -9
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
Lets pop the queued run off the queue with the set queue_name
to be 100% sure we handle the queue_name
prop correctly.
a2d21d7
to
140e4a1
Compare
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.
lgtm
…hen calling launch_add (#4625) * fix(public-api): Job uses queue_name keyword arg (instead of queue) when calling launch_add
Job uses queue_name keyword arg (instead of queue) when calling launch_add
Fixes WB-11748
Description
Fixes
Job.call()
using the wrong keyword (queue
vsqueue_name
) when calling launch_add.Testing
Unit test was added to verify
Job.call()
. Runtox -e pylaunch38 tests/unit_tests/tests_launch/test_job.py