ashb commented on PR #68662: URL: https://github.com/apache/airflow/pull/68662#issuecomment-4751194863
I think we should remove the ability to serialize/deserialize exceptions in the general case, and the specific exceptions that needs to cross the worker/supervisor boundary should be handled differently and with an explicit allow list only. Crucially code in `serialized_objects.py` can run in the in any process that deals handles serialization (which is a lot) -- and this something we need or likely want in the general case. Please can you work on removing serialization (and deser.) of exceptions via Airflow's general serialization framework in favour of something tightly scoped and targeted. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
