hterik commented on issue #43177: URL: https://github.com/apache/airflow/issues/43177#issuecomment-2425656192
Improving the stack traces sounds like an excellent idea. Similar effort was previously discussed in https://github.com/apache/airflow/discussions/20060 I still stand by that idea and think that splitting the stack trace per the different layers in the stack, rather than a number-based depth is preferable. It's not possible to pick a depth that is good for all situations and it will constantly be a moving target, in case someone decides to just make one more function call. It's better to have known cutoff-points. The `core.dagbag_import_error_traceback_depth` has that issue, picking a number too short will often leave out relevant parts. It's better to declare everything up until some point as internals, that should not be presented. To give an example, tracebacks from a python script don't contain stacks from the CPython C-code for example. -- 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]
