-
Notifications
You must be signed in to change notification settings - Fork 5
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
Jumpster #136
Conversation
Sounds good! Can you merge the latest commit from
Maybe just remove |
I was hoping somebody else could pick this up and finish it off? I have very limited time this week. What you say @PekkaSavolainen sounds right, maybe you can go ahead and do it? Sorry about that. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 0.8-dev #136 +/- ##
===========================================
+ Coverage 62.53% 62.86% +0.33%
===========================================
Files 46 43 -3
Lines 3918 3886 -32
Branches 763 765 +2
===========================================
- Hits 2450 2443 -7
+ Misses 1312 1296 -16
+ Partials 156 147 -9 ☔ View full report in Codecov by Sentry. |
Jumpster is quite good but I found a problem. After executing a Jump Link, all the items in the loop are executed in parallel. You can see the problem by executing the |
I can fix. Edit: should be better now. |
- Don't discard step from iterating active unless they finished, otherwise they might execute out of order. - Make sure steps run with the most recent output.
Execution direction was accidentally converted to string in SpineEngine._stop_item() Re spine-tools/Spine-Toolbox#2523
This PR removes the dagster dependency. It implements a new small module that does the dagster thing for us. I called it
jumpster
because it also supports jumps (i.e., loops).I have to say this was very straightforward to do, mainly code reorganization. The only thing I had to reimplement from scratch was the
get_steps_to_execute
function from theActiveExecution
class, but it was relatively simple. This is to support the point that the bit of dagster that we use is really minimal.All tests in all repositories pass but we'd probably need to test it with real workflows before merging - if we ever want to merge it. We'd also need to remove the dasgter dep from setuptools etc - I haven't done that yet - forgot how to do it - but maybe someone can help.
Fixes spine-tools/Spine-Toolbox#2523
Checklist before merging