Ash Berlin-Taylor

If we already have it in the audit log could we extract it from there in the ui/api instead of adding it to dag run table?

Yes, auditing Is messy. Both our implementation of how we currently do it in Airflow, and audit logging in general. I don't totally hate this solution, but it is only...

@dheerajturaga Where exactly would you do such an action? Also: exposing that via the `DagRun` object at runtime doesn't have to be the same way it's stored in the DB....

> actually just because adding one field to the schema which consumes a few bytes... many more fields on task instance which also would be candidated to optimize DB. We...

> @skiedude @cmarteepants My thought was to iterate through all the YML files, identify the ones that are problematic, and raise the Import error by the end, printing out the...

We might be able to fix this in Airflow 3.1 https://github.com/apache/airflow/issues/53971

If anyone is on OSX and wondering why it's not working, -- ctrl-space is the default "previous input source" hotkey https://apple.stackexchange.com/questions/423971/disable-controlspace-keyboard-shortcut so if it's on (which it is by default)...

I think queued and scheduled are distinct enough to need different colors. And skipped /upstream_failedcould be the same colour, but I don't think no_status/null should be in the same grouping....

@radujica We switched to uv recently. Something like this should work ``` uv venv uv sync --extra devel --group dev .venv/bin/pytest tests/models/test_dagbag.py::test_dagbag_dag_collection ```

`uv run` -- knew about but forgot as I'm so used to activating venvs for my workflow.