potiuk commented on PR #68511:
URL: https://github.com/apache/airflow/pull/68511#issuecomment-4880039741

   > I’m not exactly sure but this can potentially block exception classes that 
the user creates but not eagerly imported? Like lazy imports in a plugin? I did 
not think it entirely though to be honest, but building an allow list on launch 
smells wrong in a dynamic environment like Python.
   
   IMHO it prevents some classes of issues - especially that we ware taking 
about deserialisation - so potentially passing an exception that has not been 
imported by Scheduler **yet**. It is a "defense-in-depth" really, nothing 
exploitable.


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

Reply via email to