Closed
Conversation
(cherry picked from commit f3ced9a)
Remove release notes for releases >2.5 years. Users can always check versioned docs for it. (cherry picked from commit 97913b0)
Follow-up of apache#50300 for running a single task. (cherry picked from commit 3a9858e)
…he#50962) (apache#50967) (cherry picked from commit dbe707c) Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
…th schedule. (apache#50969) (apache#50970) (cherry picked from commit f8c8200) Co-authored-by: Karthikeyan Singaravelan <tir.karthi@gmail.com>
…pache#50947) (apache#50954) (cherry picked from commit 5796536) Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
(cherry picked from commit d80a711) https: //github.com/astral-sh/uv/releases/tag/0.7.7 Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
…nd (apache#50895) (apache#50998) (cherry picked from commit 98f9181) Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
…apache#50834) (apache#50988) (cherry picked from commit bca010b) Co-authored-by: Karthikeyan Singaravelan <tir.karthi@gmail.com>
I changed it to `no` as I had to change 100s of tests when porting over task.test & ti.run (cherry picked from commit 341ab09)
…1029) (apache#51030) Image verification runs in parallell, and whne they are using same venv with `uv run` they can override each other's directories while installing packaegs. (cherry picked from commit 130cd46) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…a` example (apache#50768) (apache#51000) This PR fixes an inconsistency in the `assets.rst` documentation example. The sample code used a plain string for the `alias` argument in `Metadata()`, which in reality raises: > TypeError: Key should be either an asset or an asset alias, not <class 'str'> This change updates the example to use a typed `AssetAlias("my-task-outputs")`, matching the SDK API and avoiding that error. (cherry picked from commit ed67114) Co-authored-by: QBidolet <52286815+QBidolet@users.noreply.github.com>
(cherry picked from commit 958f77f) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
(cherry picked from commit 422388f) Co-authored-by: Jens Scheffler <95105677+jscheffl@users.noreply.github.com>
…che#51051) (apache#51053) (cherry picked from commit e7a90d6) Co-authored-by: Jens Scheffler <95105677+jscheffl@users.noreply.github.com>
…om access is needed (apache#50641) (apache#50950) * fix(task_instances): handle upstream_mapped_index when xcom access is needed * style(expand_input): fix expand_input and SchedulerExpandInput types * test(task_instances): add test_dynamic_task_mapping_with_parse_time_value * test(task_instance): add test_dynamic_task_mapping_with_xcom * style: import typing * style: move the SchedulerExpandInput into type checking block * Revert "style: move the SchedulerExpandInput into type checking block" This reverts commit c2c87ca. (cherry picked from commit 5458e7e) Co-authored-by: Wei Lee <weilee.rx@gmail.com>
…pache#51057) (apache#51111) (cherry picked from commit 1a34a42) Co-authored-by: Guan Ming(Wesley) Chiu <105915352+guan404ming@users.noreply.github.com>
* Fix bulk api annotation * Small improvement --------- (cherry picked from commit 3208bbb) Co-authored-by: Guan Ming(Wesley) Chiu <105915352+guan404ming@users.noreply.github.com>
(cherry picked from commit 8bee3fb) Co-authored-by: Guan Ming(Wesley) Chiu <105915352+guan404ming@users.noreply.github.com>
…) (apache#51172) Previously it was missing dag_id filter, but joining on start date would still be problematic. In this PR I refactor the query a bit so that all joins are guaranteed 1-1. To get "latest" DagRun I sort by the DagRun.id column. This is a simplifying assumption that would be more performant than sorting by start_date, since there could be more than 1 dag run with a given start date. (cherry picked from commit b994bb2) Co-authored-by: Daniel Standish <15932138+dstandish@users.noreply.github.com>
* Add Execution API versioning docs for Contributors (apache#50539) Added our versioning strategy for Task Execution API in Contributing Guide. (cherry picked from commit 188e225) * Refine the execution api versioning doc to reflect reality (apache#51152) (cherry picked from commit f7ceec4) --------- Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
… as flaky (apache#51193) (apache#51198) Fixes apache#50474 (hopefully) (cherry picked from commit 066f978) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
) (apache#51199) When using `dag.test()` with deferred tasks, tasks that complete their trigger execution were incorrectly being set to `SUCCESS` state instead of `SCHEDULED` state. This prevented task resumption! Dag used to test: ```python from datetime import datetime, timedelta, timezone from typing import Any import pendulum from airflow.providers.standard.triggers.temporal import DateTimeTrigger from airflow.sdk import Context, task, BaseOperator, DAG class DummyOperator(BaseOperator): def execute(self, context: Context): self.defer( trigger=DateTimeTrigger( moment=datetime.now(timezone.utc) + timedelta(seconds=2), ), method_name="execute_complet", ) def execute_complet(self, context: Context, event: Any = None): assert event is not None return "test" @task def dummy_task(param): print("DEBUG") assert param == "test", "Parameter should be 'test'" with DAG( dag_id="example_debug", start_date=pendulum.datetime(2021, 1, 1, tz="UTC"), ) as dag: task1 = DummyOperator(task_id="task1") task2 = dummy_task(task1.output) task1 >> task2 if __name__ == "__main__": dag.test() ``` (cherry picked from commit 1b83f71) Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
…ckage (apache#51192) (apache#51220) As we are working on a longer-term solution for example-dags, the short-term one is to bring the standard example_dags back to the airflow-core via symbolic link to the standard package folder. This makes the dags to be copied to the airflow-core from the latest main version (but those dags don't change) while not requiring to duplicate the dags and keep them in standard provider where the documentation for them is kept. (cherry picked from commit 46908a1) Co-authored-by: Jarek Potiuk <jarek@potiuk.com> Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
shreyaskj-0710
requested review from
Fokko,
XD-DENG,
amoghrajesh,
bbovenzi,
bolkedebruin,
bugraoz93,
dstandish,
eladkal,
ephraimbuddy,
gopidesupavan,
hussein-awala,
jason810496,
jedcunningham,
josh-fell,
jscheffl,
kaxil,
mik-laj,
mobuchowski,
o-nikolas,
pierrejeambrun,
potiuk,
rawwar,
ryanahamilton,
shubhamraj-git,
uranusjr and
vincbeck
as code owners
Member
|
This change has many unrelated commits and the name is just wrong. If you want to submit a change - make sure to base it on top of main and choose a good name for the PR |
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #54200
Description
Previously, both localStorage and cookies were used to manage the current session for the JWT token. When accessing
multiple Airflow instances from the same browser, this caused an Invalid token error.
To resolve this, I replaced the use of localStorage and cookies with sessionStorage.
Pros
Allows users to log in to multiple Airflow instances from the same browser without token conflicts.
Cons
When opening a new browser tab for an Airflow instance, users will need to re-enter their credentials.