We’re experiencing a bit of an issue when attempting to add the

connection_to_freshness_policy_fn

to existing Airbyte assets. On Dagster version 1.1.11, and dagster-airbyte

0.17.11

The stack trace when we attempt to materialize those assets after adding the following

connection_to_freshness_policy_fn=lambda _: FreshnessPolicy(maximum_lag_minutes=60),

Stack Trace:
  File "/usr/local/lib/python3.8/site-packages/dagster/_core/executor/multiprocess.py", line 240, in execute
    event_or_none = next(step_iter)
,  File "/usr/local/lib/python3.8/site-packages/dagster/_core/executor/multiprocess.py", line 357, in execute_step_out_of_process
    for ret in execute_child_process_command(multiproc_ctx, command):
,  File "/usr/local/lib/python3.8/site-packages/dagster/_core/executor/child_process_executor.py", line 174, in execute_child_process_command
    raise ChildProcessCrashException(exit_code=process.exitcode)