Open
Conversation
Reverting back to installing packages using pip3 with homebrew.
This means, we can now use Amazon S3 to store inputs & outputs of each task! Known issue: local memory reference counts might not be consistent because they are not included in serialized EvalWorkEntry, and thus later tasks/ops are not aware of these existing reference counts.
and column size wider than task size When grabbing source task, we assume the source task only has one output column and it is the last one fed into EvalWorkEntry.
to support gcs / s3
willcrichton
force-pushed
the
master
branch
2 times, most recently
from
6822cde to
5d4d222
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi Alex,
scanner/engine/scheduler.hcontains my prototype of the new scheduler. Please take a look and let me know if you have any comments.