squashed into https://dagster.phacility.com/D6133

squashed into https://dagster.phacility.com/D6133

squashed into https://dagster.phacility.com/D6133

squashed into https://dagster.phacility.com/D6133

squashed into https://dagster.phacility.com/D6133

up

up

up

up

up

up

Very excited to see this land. Will defer to dish on the deets of the js.

adding @sandyryza here. I think this makes a lot of sense and I don't think having the events be left-to-right and the graphs right-to-left is a big problem but open to other's perspective

• Instead of flipping, scroll the asset materialization grid to the right by default
• Fix React warnings in the useViewport component, some useCallback's missing

"As initialized upon program startup, the first item of this list, path[0], is the directory containing the script that was used to invoke the Python interpreter. If the script directory is not available (e.g. if the interpreter is invoked interactively or if the script is read from standard input), path[0] is the empty string, which directs Python to search modules in the current directory first."

"I'm pretty resistant to directions that involve using type annotations for anything other than annotating the actual Python type that's expected somewhere. It's fairly abusive of a Python language feature, and it causes non-trivial trouble for anyone who's trying to use that language feature in the correct way."

possibly relevant:

I like the variants you listed that involve overloading the input_defs arg on solid.  I think that kind of overloading is pretty Pythonic / expected. When reading that code, it's very difficult to misinterpret what's going on.

up

up