[03:08:58] ^ cool, FWIW you should make the change-id of that patch equal to the previous patch so it's not a separate change request [10:13:07] weekly status update published to https://app.asana.com/0/0/1204257215822763 and on wiki https://wikitech.wikimedia.org/wiki/Search_Platform/Weekly_Updates/2023-03-24 [10:58:22] lunch [15:02:40] o/ ebernhardson: I wonder why I see merge conflicts for mediawiki_revision_recommendation_create DAG. Did you migrate that too? [16:16:48] https://gitlab.wikimedia.org/repos/data-engineering/airflow-dags/-/merge_requests/319 [16:17:38] pfischer: hmm, checking [16:19:24] pfischer: ahh, yes in https://gitlab.wikimedia.org/repos/data-engineering/airflow-dags/-/merge_requests/318 . Basically i was looking to turn on the transfer_to_es dag and that uses ExternalTaskSensor's that depend on this dag as well [16:23:18] makes me wonder if ExternalTaskSensor is really our best bet for these kinds of things, having them all tied together means that we can turn any of them on until all of them are ready to turn on. Can't be turned on in the new instance piece-meal. [16:24:41] but i suppose migrating dags between repos is also a relatively rare event, likely not worth optimizing for [17:52:17] lunch, back in ~45 [17:55:29] ebernhardson: alright, I’ll close my PR then. [18:47:55] back [21:20:21] everything except glent should be turned on now in the new airflow deployment, glent had a spark3 transition bug and will need to release a new jar next week but i've done a test run with the -SNAPSHOT and it seems fine. [21:47:48] Getting closer on the ban logic...no elastic client stuff there yet though https://gerrit.wikimedia.org/r/c/operations/cookbooks/+/902502