-
Notifications
You must be signed in to change notification settings - Fork 931
Feature: Support spinning a single metaflow step (Rebased) #2506
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
Conversation
| # queries on that same TaskDatastore will be quick (since we already | ||
| # have all the metadata) | ||
| self._task_metadata_caches = OrderedDict() | ||
| # have all the metadata). We keep track of this in a file so it persists |
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.
I wonder if same should be done for self._store_caches? which is right now an OrderedDict
4e80bfa to
94aa6d6
Compare
e785d31 to
4d0ad94
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.
Some smallish comment with maybe a small concern around the transfer of artifacts.
241af68 to
3a36e8b
Compare
8652c80 to
e15c14d
Compare
To test
spinon a new flow you can do the following:Simple case:
Pass in specific pathspec:
Pass in custom artifacts via module:
Skip decorators (including the whitelisted ones):
Use with Runner API:
See the tests for more examples on hot to use this command.