Are we exposing or documenting stuff under dagster.core.host_representation like ManagedGrpcPythonEnvRepositoryLocationOrigin, LoadableTargetOrigin, and PipelineSelector, which have been mentioned in this example?
Should we? Without linking to detailed API docs or further explanation, it could be a bit hard for users to digest what's going on when using these suggested APIs. cc @dgibson: as you may have more context in this corner of the codebase.
Today
Today
sashank requested review of D6138: (docs-infra-2/n) Write script to pack API docs data.
sashank published D6137: (docs-infra-1/n) Clean up docs directory and move sphinx to subdirectory for review.
yuhan updated subscribers of D5949: Add an example of how to trigger a pipeline by graphQL.
yuhan added inline comments to D6048: [Memoized Dev Example 2/2] Memoized development example.
dgibson updated the diff for D6133: Reconstruct ExecutionPlan from the ExecutionPlanSnapshot in the run worker if one exists.
up
dgibson updated the diff for D6133: Reconstruct ExecutionPlan from the ExecutionPlanSnapshot in the run worker if one exists.
up
Yesterday
Yesterday
squashed into https://dagster.phacility.com/D6133
squashed into https://dagster.phacility.com/D6133
squashed into https://dagster.phacility.com/D6133
dgibson abandoned D6086: [5/n] Wait to determine step compute_fn until you're actually in step execution.
squashed into https://dagster.phacility.com/D6133
squashed into https://dagster.phacility.com/D6133
dgibson retitled D6133: Reconstruct ExecutionPlan from the ExecutionPlanSnapshot in the run worker if one exists from (Squashed) Reconstruct ExecutionPlan from the ExecutionPlanSnapshot to Reconstruct ExecutionPlan from the ExecutionPlanSnapshot in the run worker if one exists.
dgibson updated the diff for D6133: Reconstruct ExecutionPlan from the ExecutionPlanSnapshot in the run worker if one exists.
up
dgibson updated the diff for D6133: Reconstruct ExecutionPlan from the ExecutionPlanSnapshot in the run worker if one exists.
up
dgibson updated the diff for D6133: Reconstruct ExecutionPlan from the ExecutionPlanSnapshot in the run worker if one exists.
up
dgibson updated the diff for D6133: Reconstruct ExecutionPlan from the ExecutionPlanSnapshot in the run worker if one exists.
up
dgibson updated the diff for D6133: Reconstruct ExecutionPlan from the ExecutionPlanSnapshot in the run worker if one exists.
up
dgibson updated the diff for D6133: Reconstruct ExecutionPlan from the ExecutionPlanSnapshot in the run worker if one exists.
up
Increase UI sensor polling rate
catherinewu published D6134: Increase UI sensor polling rate for review.
Very excited to see this land. Will defer to dish on the deets of the js.
Sat, Jan 23
Sat, Jan 23
schrockn added a comment to D6029: Flip asset materialization UI so newest time/partition is on the left.
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
schrockn added a reviewer for D6029: Flip asset materialization UI so newest time/partition is on the left: sandyryza.
bengotow requested review of D6132: UI support for dynamic outputs, Run view state cleanup.
bengotow updated the diff for D6029: Flip asset materialization UI so newest time/partition is on the left.
- Instead of flipping, scroll the asset materialization grid to the right by default
- Fix React warnings in the useViewport component, some useCallback's missing
dgibson added a comment to D6131: Replace dagster api grpc with 'python -m dagster.grpc' in docs?.
"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."
schrockn added a comment to D5115: don't error on solid type annotations that don't resolve to dagster types.
"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."
dgibson added a comment to D6131: Replace dagster api grpc with 'python -m dagster.grpc' in docs?.
possibly relevant:
dgibson committed R1:ac7dec89ecca: Remove pipeline_def from top-level SystemExecutionContext, only use in step… (authored by dgibson).
Remove pipeline_def from top-level SystemExecutionContext, only use in step…