Hi team, I am trying to access here https://docs.dagster.io/_apidocs/libraries/dagster_mlflow but it is not working anymore. It will be/was depecrated?

Hey is there anyway to use Union for input definitions and have something like this?

@solid(input_defs=[InputDefinition(name="current", dagster_type=Union[Series, int, float]), InputDefinition(name="previous", dagster_type=Union[Series, int, float])])

Hi team. Got a question I wasn't able to quickly figure out through the docs - is it possible to specify a different

run_launcher

for different repositories within a workspace? What would be the way to configure this behaviour?

quick question since i find the docs a bit overwhelming , if id like to create a super simple single machine deployement can i just take my local dagster project repo and clone it to the ec2 server and run dagit and dagster daemon in it?

this is before calling devops and i a bit confused to which parts of the example i deploy and which i dont

i see i need the dagster.yaml workspace.yaml and the code so essentially i could simple copy my dagster home and code and run dagit in the repo dir

basedir in dagster.yaml should be the workspace.yaml dir?

hi D friends! we are trying to set up parallel execution in one of our pipelines, but seem to be losing access to environment variables when we run it this way, which is causing things to fail. has anyone else run into this/figured out a way to solve? thanks!

Is there a way to access the mode name in a solid? (I want to invoke a pipeline through graphql in the same mode)

Hi all, I'm playing around with sensors and using the docker-ecs example. I have daemon, pipelines, and dagit containers running. I do not know why, but my dagit instance always says that the sensor daemon is not running. Any idea how to solve this?

when passing dagster scheduel execution_timezone="IL" i get an error although wikipedia indeicates that is the right format

are you using the pytz timezone to parse it?

need to use Israel and not IL. (should point the documentation to the pytz all_timezones list for 😛

i am not sure i understand why , but it looks like passing mode="prod" gets ignored when i scheduel a pipeline... i get an error saying mode default doesnt exist for the pipeline which is true but i configured it to use mode "prod"

@hourly_schedule(
    pipeline_name="athena_table_creation",
    start_date=datetime(2021, 1, 1),
    execution_timezone="UTC",
    mode="prod"
)
def my_hourly_schedule(_context):
    run_config = {"resources": {...}, "solids": {...}}

    return run_config

the pipeline config looks as follows:

MODE_PROD = ModeDefinition(name="prod", resource_defs={
    "athena_connection": athena_connection,
    "s3": s3_resource
})
MODE_TEST = ModeDefinition(name="test", resource_defs={
    "athena_connection": athena_connection,
    "s3": s3_resource
})
@pipeline(mode_defs=[MODE_PROD, MODE_TEST])
def athena_table_creation():
    """ implementation reducted """

error:

dagster.check.CheckError: Failure condition: Could not find mode default in pipeline athena_table_creation
  File "/home/ubuntu/Envs/dagster/lib/python3.8/site-packages/dagster/grpc/impl.py", line 342, in get_external_execution_plan_snapshot
    create_execution_plan(
  File "/home/ubuntu/Envs/dagster/lib/python3.8/site-packages/dagster/core/execution/api.py", line 718, in create_execution_plan
    resolved_run_config = ResolvedRunConfig.build(pipeline_def, run_config, mode=mode)
  File "/home/ubuntu/Envs/dagster/lib/python3.8/site-packages/dagster/core/system_config/objects.py", line 166, in build
    run_config_schema = pipeline_def.get_run_config_schema(mode)
  File "/home/ubuntu/Envs/dagster/lib/python3.8/site-packages/dagster/core/definitions/pipeline.py", line 292, in get_run_config_schema
    mode_def = self.get_mode_definition(mode)
  File "/home/ubuntu/Envs/dagster/lib/python3.8/site-packages/dagster/core/definitions/pipeline.py", line 357, in get_mode_definition
    check.failed(
  File "/home/ubuntu/Envs/dagster/lib/python3.8/site-packages/dagster/check/__init__.py", line 119, in failed
    raise CheckError("Failure condition: {desc}".format(desc=desc))

does it have to do with        executor_defs field of the mode definition?

weird , it should be multi and inprocess by default, how does the daemon select the right execution definition without me stating it

I’m having trouble getting the

dbt_rpc_run_and_wait

solid to retry when it hits the dbt RPC server while it’s compiling 🧵

I have two questions: 1. Can you actually pass as parameters serialized data between solids? 2. Is there any way to connect pipelines between them?

what does , an axis of pipeline in the documentation mean when referring to partitions?

is it implicitly suggesting dagster will run it in parallel if the excutor is docker/k8s/ecs/dask?

Hi there! Anybody knows how to run dagit as a daemon?

Hi all, we're trying to migrate our dagster instance from 0.12.2 to 0.12.4 but it is stuck at the following stage. Do you have any guidance on how to fix this ? Many thanks !

Can

DockerLauncher

take envs from repository container? Because now i see two ways how pipeline container can inherit envs: 1. DagsterDaemon has these envs inside himself. 2. All envs are embedded into repository image, so pipeline image has all envs embedded (pipeline image is the same as repository image) IMHO, both are not good

In the new ops API, do you still have to yield `Outputs`s when you have multiple outputs?

i am currently testing out the backfills , was wondering if there is a way to pass a different config per env and maybe more than one value in the partitioon

i am passing my solid a target bucket per environment and a table to go over, for me in this context table is the partition and target bucket only changes per environment , is there a way to do it with backfills?

https://docs.dagster.io/concepts/partitions-schedules-sensors/partitions#defining-a-partition-set here in the example there is a config function but i dont see how it gets context parameters

is there docs on that?>

Hi Team. We Deployed user-code-deployment  with dagster official helm chart but we are getting below error in dagit :

rpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:

status = StatusCode.UNAVAILABLE details = "no healthy upstream" debug_error_string = "{"created":"@1634031954.613875382","description":"Error received from peer ipv4192.168.125.1483030","file":"src/core/lib/surface/call.cc","file_line":1067,"grpc_message":"no healthy upstream","grpc_status":14}" This our workspace.yaml and gateway yaml files in helm. in gateway we configured Istio things to access our dagit ui. Please help us to resolve this error.