Jens Scheffler
Jens Scheffler
> @jscheffl Could you verify your changes again -- I needed to force-push on v2-10-test to sync it back with v2-10-stable. Uuf, I think I can do this later. But...
Note: Marking as DRAFT as I assume some pytests fail and need to be adjusted.
> 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? Fiddeling this out...
> I have a general qn regarding the way we are handling things here. > > The `getuser` function uses `getpass.getuser()` to get the username of the current user and...
> Point being -- adding a try / except would do no harm, but I'll let you take a call on that Added handling for the problem in https://github.com/apache/airflow/pull/51738/commits/4fe66fc8619d55b52472e213e7da6d9e50935d62
I have the use case as well that on the homepage/dashboard a user would also like to see "The Dag Runs I have triggered" which would be a mess if...
A lot of debate about the triggering user ... actually just because adding one field to the schema which consumes a few bytes... many more fields on task instance which...
If a PR/fix is available we also need to add this to PR for version 2.10 in PR https://github.com/apache/airflow/pull/42788 (or on the same branch)
It is helping users who try to contribute but (by accident an old interpreter in the $PATH or just have not read the docs) that the root cause can be...
I am not sure whether this PR is a good idea. When this is merged you basically break compatibility with Airflow 2.10/2.11