The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

:wave:

Hi again!  We recently bumped Dagster up to 1.1.15 (as well the dagster-airbyte library to 0.17.15), and we’re still seeing the executor exception `ChildProcessCrashException`  :thread:

```Multiprocess executor: child process for step airbyte_sync_63c3b unexpectedly exited with code 1.
dagster._core.executor.child_process_executor.ChildProcessCrashException

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)```

If I comment out the `connection_to_freshness_policy_fn` in the `load_assets_from_airbyte_instance` , it runs as intended.

Hi Dusty, sorry this is still happening! Let me try to see if I can replicate

No apologies needed! Let me know what else you might need from my end.

Hi Dusty, hoping today’s release will fix this issue for good, we patched a serialization issue with freshness policies

All good!  We’ve been attaching freshness policies on downstream assets and it seems to be holding us over for now.

I’m curious if there’s been any movement on the <https://github.com/dagster-io/dagster/issues/11531#issuecomment-1376142023|Dagster/Airbyte reconciliation errors I was seeing>?

Looks like the Freshness bug has been fixed on 1.1.18, btw