Daniel Standish
Daniel Standish
@RNHTTR you might be good person to review from the perspective of "are these circumstances where user would otherwise not have insight into what happened to the task" slash "are...
> @Lee-W @uranusjr - Apologies for all of the back-and-forth on testing, but could you help me understand why this test is failing `Tests / Non-DB tests / Non-DB::3.8: Always...
> Yes. That's exactly how I envisioned solving this problem. @dstandish ? IIRC this should be fine when task done but may present challenges when task is in flight because...
> @dstandish With the changes introduced in PR #43183, is it still feasible to generate logs from locations other than the workers? If so, could you please provide a few...
> @dstandish With the changes introduced in PR #43183, is it still feasible to generate logs from locations other than the workers? If so, could you please provide a few...
TaskContextLogger is removed from airflow; this PR needs to be updated to use the log table. The feature was added in this pr https://github.com/apache/airflow/pull/40867 and you can see an example...
> I'm not a pycharm user, but @kaxil @dstandish can provide some insight. Anything in particular you wanted me to look at?
possible solutions 1. use locking when running get-or-create-apdr. Somehow we would need to use locking so that the two writers would not both see no apdr record and thus both...
@potiuk another option is to make another dedicated lock table like an "apdr_mutex" table which would control only the creation of new APDR records. this would have the same effect...