Preliminary to further work on distributed logging
- R1 dagster
Lint Warnings Excuse: wip Severity Location Code Message Warning python_modules/dagster-graphql/dagster_graphql/implementation/pipeline_run_storage.py:146 W0612 Unused Variable
No Unit Test Coverage
for your consideration in follow ups - --log is a bit goofy of a set up for determining storage, we should come up with a more explicit scheme. dagit --storage fs or something like that
kinda feel like we can drop pipeline here, RunStorage communicates whats going on just as effectively imo.
this is used by both dagster-graphql and dagit now so this err message is stale. Also could do a better job communicating that its just moving on instead of failing outright
while a small code change, this is a pretty big system change - can you explain what the motivation here is? Just want to make sure we think through this since I reckon theres no going back as something will depend on these ids quickly.
yep, i am trying to make sure we have a way to tell if we've seen an event record before or not. i think this will simplify the case where we have two dagit processes writing/reading from a shared filesystem run storage
I'm inclined to punt this until we know the exact constraints of what we are trying to solve, for example I can imagine choosing a different scheme than uuid