I've noticed that if a dagster run is deleted within k8s (while obviously not the preferred termination strategy), runs page no longer renders properly

Operation name: RunsRootQuery

Message: Cannot return null for non-nullable field Run.mode.

Path: ["pipelineRunsOrError","results",5,"mode"]

Locations: [{"line":29,"column":3}]

Stack Trace:
  File "/usr/local/lib/python3.7/site-packages/graphql/execution/execute.py", line 541, in execute_field
    return_type, field_nodes, info, path, result
  File "/usr/local/lib/python3.7/site-packages/graphql/execution/execute.py", line 621, in complete_value
    "Cannot return null for non-nullable field"

I think this is due to a bug / backcompat issue that will go away if dagit / the helm chart is upgraded to 1.3.2 or later.

this is possible. this happened on a test db, where i forward migrated it