wave Hi again We recently bumped Dagster up to 1 1 15 as wel

Question

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

Dusty Shapiro · Answer

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

Dusty Shapiro · Answer

If I comment out the `connection to freshness policy fn` in the `load assets from airbyte instance` it runs as intended

ben · Answer

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

Dusty Shapiro · Answer

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

ben · Answer

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

Dusty Shapiro · Answer

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

Dusty Shapiro · Answer

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>

Dusty Shapiro · Answer

Looks like the Freshness bug has been fixed on 1 1 18 btw