User Details
- User Since
- Feb 28 2020, 11:37 PM (47 w, 2 d)
Sat, Jan 23
Fri, Jan 22
Thu, Jan 21
resigning as the adoption folks have more context to sign off the copy :)
Wed, Jan 20
Tue, Jan 19
Fri, Jan 15
done re-release with this change just now
Thu, Jan 14
Wed, Jan 13
lg2m. had comments about mentioning the version number
lg2m. will let max sign off
for posterity, this would address one of the follow ups listed in D5922
Tue, Jan 12
merged in D5474
comments
handle_back_compat for AssetStoreOperation
up
up
up
lg2m. but i don't feel strongly either way so i defer to people who hold stronger opinions :)
yield DagsterEvent in load_input_value
up
@sandyryza re:
The pattern that we had with ObjectStoreOperation where we put the obj on it and then call serializable to strip it out is a little confusing. Now that the user code isn't responsible for generating the event, do we need this pattern anymore?
without this pattern, we would involve DagsterEvent in the inputs.py.
rebase only
I like LoadResult
rebase
resource_instances_to_override
guard all log.dagster_event.event_type_value with log.is_dagster_event
up
up
up
up
up
Mon, Jan 11
rebase