Hi After upgrading dagster from `0 15 2` to `0 15 5` our ` r

Question

Hi After upgrading dagster from `0 15 2` to `0 15 5` our ` run status sensor` annotated method is failing with `dagster check CheckError Member of list mismatches type` details in thread

David · Answer

```2022 07 12 17 00 09 +0900 dagster daemon SensorDaemon ERROR Sensor daemon caught an error for sensor on graph success dagster core errors SensorExecutionError Error occurred during the execution of evaluation fn for sensor on graph success Stack Trace File Users dpursehouse git project venv lib python3 10 site packages dagster grpc impl py line 284 in get external sensor execution with user code error boundary File Users dpursehouse git project homebrew Caskroom miniforge base envs nodejs 16 6 1+python 3 10 0 lib python3 10 contextlib py line 153 in exit self gen throw typ value traceback File Users dpursehouse git project venv lib python3 10 site packages dagster core errors py line 191 in user code error boundary raise error cls The above exception was caused by the following exception dagster check CheckError Member of list mismatches type Expected lt class dagster core definitions run request SkipReason gt lt class dagster core definitions run request RunRequest gt lt class dagster core definitions run request PipelineRunReaction gt Got DagsterRun pipeline name= pipeline name run id= b8ed68e9 144e 4209 b736 e4ff158e010d run config= resources task data config mode= default asset selection=None solid selection=None solids to execute=None step keys to execute=None status= lt DagsterRunStatus SUCCESS SUCCESS gt tags= dagster grpc info host localhost port 4266 dagster scheduled execution time 2022 07 12T07 35 00+00 00 dagster schedule name pipeline every five minutes root run id=None parent run id=None pipeline snapshot id= eb8ce46ea6dcc07b761a6d3f089b6f7d0df81c34 execution plan snapshot id= 35c1ae10b8ffbbf04fc6b4a739eedab59ac3b975 external pipeline origin=ExternalPipelineOrigin external repository origin=ExternalRepositoryOrigin repository location origin=GrpcServerRepositoryLocationOrigin host= localhost port=4266 socket=None location name= project pipelines repository use ssl=None repository name= project pipeline name= pipeline pipeline code origin=PipelinePythonOrigin pipeline name= pipeline repository origin=RepositoryPythonOrigin executable path= Users dpursehouse git project venv bin python code pointer=PackageCodePointer module= project pipelines repository attribute= project working directory= Users dpursehouse git project container image=None entry point= dagster container context= of type lt class dagster core storage pipeline run DagsterRun gt Stack Trace File Users dpursehouse git project venv lib python3 10 site packages dagster core errors py line 184 in user code error boundary yield File Users dpursehouse git project venv lib python3 10 site packages dagster grpc impl py line 289 in get external sensor execution return sensor def evaluate tick sensor context File Users dpursehouse git project venv lib python3 10 site packages dagster core definitions sensor definition py line 373 in evaluate tick check is list result SkipReason RunRequest PipelineRunReaction File Users dpursehouse git project venv lib python3 10 site packages dagster check init py line 862 in is list return check iterable items obj of type list File Users dpursehouse git project venv lib python3 10 site packages dagster check init py line 1597 in check iterable items raise CheckError ```

David · Answer

This is happening on a pipeline that is being invoked on a 5 minute schedule

David · Answer

Seems to be because the sensor is being called with a `DagsterRun` while it expects one of the other types ```check is list result SkipReason RunRequest PipelineRunReaction ```

David · Answer

Has something changed in dagster that causes this I m not sure what we need to change in our code to fix this

David · Answer

I ve narrowed it down to `0 15 3` that introduces this issue

yuhan · Answer

Hi do you mind sharing your sensor code

David · Answer

I can t share the exact code but here s the gist of it ``` run status sensor pipeline run status=DagsterRunStatus SUCCESS minimum interval seconds=10 default status=DefaultSensorStatus RUNNING def on graph success context RunStatusSensorContext gt SkipReason | PipelineRunReaction On success Redacted code here does some stuff in our database not using any dagster APIs return PipelineRunReaction context dagster run ```

yuhan · Answer

Got it trying to repro on my end

David · Answer

< yuhan> were you able to reproduce this To add a bit more context we have a ` graph` that we are configuring to run on a schedule like this returned in the `schedules` field of the return value from our ` repository` method ``` graph every five minutes ScheduleDefinition name= graph every five minutes description= Process every five minutes job=graph every five minutes job cron schedule= 5 execution timezone= US Pacific run config=dagster build run config default status=DefaultScheduleStatus RUNNING ``` `graph every five minutes job` is the result of calling `to job ` on the ` graph` and `dagster build run config ` is a locally implemented method that sets up some resource configs

yuhan · Answer

sorry got distracted by other stuff i wasnt able to repro on my first try but will dig in first thing tomorrow

David · Answer

Thanks Appreciate the help

sandy · Answer

< jamie> you recently made some changes to run status sensor right Could this possibly be related

jamie · Answer

could potentially be related i ll look into it

jamie · Answer

< David> just wanted to let you know i am able to replicate the issue in 0 15 3 still trying to figure out why this is happening but i ll keep you updated on my progress

David · Answer

Thanks < jamie>

jamie · Answer

quick update I found the issue and have a PR up for it It unfortunately won t make it in time for this week s release but it ll go out next week Thanks for reporting this and being patient while we figured it out

David · Answer

That s great news thanks < jamie> No problem to wait until next week

David · Answer

Just to follow up on this we installed dagster 0 15 8 which included the fix and now it works fine Thanks again for investigating and fixing