19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
#dagster-airbyte
Title
# dagster-airbyte
d
Dusty Shapiro
02/03/2023, 8:04 PM👋
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 Copy code
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_fnload_assets_from_airbyte_instanceb
ben
02/03/2023, 9:05 PMHi Dusty, sorry this is still happening! Let me try to see if I can replicate
d
Dusty Shapiro
02/03/2023, 9:07 PMNo apologies needed! Let me know what else you might need from my end.
b
ben
02/08/2023, 11:57 PMHi Dusty, hoping today’s release will fix this issue for good, we patched a serialization issue with freshness policies
d
Dusty Shapiro
02/09/2023, 12:28 AMAll 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 Dagster/Airbyte reconciliation errors I was seeing?
Looks like the Freshness bug has been fixed on 1.1.18, btw
4 Views