-
Notifications
You must be signed in to change notification settings - Fork 301
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
try removing multiple imports to resolve fast-mode issue #2110
Conversation
Signed-off-by: novahow <[email protected]>
Thank you for opening this pull request! 🙌 These tips will help get your PR across the finish line:
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2110 +/- ##
===========================================
+ Coverage 71.79% 85.81% +14.01%
===========================================
Files 182 313 +131
Lines 18561 23503 +4942
Branches 3654 3511 -143
===========================================
+ Hits 13326 20169 +6843
+ Misses 4592 2726 -1866
+ Partials 643 608 -35 ☔ View full report in Codecov by Sentry. |
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.
cc @cosmicBboy mind taking a look
Signed-off-by: novahow <[email protected]> Co-authored-by: Kevin Su <[email protected]> Signed-off-by: bugra.gedik <[email protected]>
Signed-off-by: novahow <[email protected]> Co-authored-by: Kevin Su <[email protected]> Signed-off-by: Jan Fiedler <[email protected]>
Tracking issue
flyteorg/flyte#4716
Why are the changes needed?
Please refer to may example in flyteorg/flyte#4716 (comment)
When we have a python file that contains workflows, tasks, and launch plans and try to run that in fast mode, we get an error:
AssertionError: The cached values aren't the same as the current call arguments
This happens because when executing the file, the launch_plan's
get_or_create
method is invoked by the following snippet multiple times, thus theLaunchPlan.CACHE
stores a workflow. After that when we're really creating a plan withstandard_scale_launch_plan = LaunchPlan.get_or_create(
, the workflow of the plan is different from the workflow of the cached plan, which I haven't figured out the reason.What changes were proposed in this pull request?
My workaround is removing
exec_module
in the try block andimport_module
in the exception block so thatget_or_create
won't be invoked multiple timesHow was this patch tested?
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link