Jarek Potiuk

You need to rebase, and fix static checks that are resulting from switching to the new databricks provider.

Let me add to it what I wrote about OTEL in the https://lists.apache.org/thread/b2bvn8sbxfncg9qpvry9w142944mnlj6 - this might be a great tool to hlep with things. I a not sure if I...

> @omkar-foss The main question is who the target audience of the research is, where possible answers are: maintainers, contributors, power users, general public, etc. Based on @kaxil's instructions, I'd...

I think none of the maintainers know "power users" well. Almost by definition, we are not running, nor maining airlfow and we do not have teams of people working together...

I also looked at it - and actually I have a comment a bit contrary to those early comments of @amoghrajesh who insisted on "choice" answers. Since we are not...

Also see https://github.com/apache/airflow/pull/40802#issuecomment-2468032255 discussion. I believe with OTEL and traces (and even including limited set of logs in the traces) we are closer to address big gap in debugging of...

I'd agree with @konstin - and that's something that **might** be useful for Airflow. For development, even for regular running of the tests, having single .venv where you can install...

I think it makes sense to add **some** indication in the tree output when there are some transitive dependencies in the package and we do not show them. Nut it...

> @potiuk - I believe that's fixed on main (omitting * for packages with no dependencies). Ups. you are moving too fast ... I only saw that while catchng up...

> Also note the commentary here is about the footnote explaining of the _meaning_ of `*` not including it at all. Understood. Yeah. That makes perfect sense.