Skip to content

Conversation

@22quinn
Copy link
Contributor

@22quinn 22quinn commented Jul 19, 2020

Fixes the question posted at #9699 (comment)


Make sure to mark the boxes below before creating PR: [x]

  • Description above provides context of the change
  • Unit tests coverage for changes (not needed for documentation changes)
  • Target Github ISSUE in description if exists
  • Commits follow "How to write a good git commit message"
  • Relevant documentation is updated including usage instructions.
  • I will engage committers as explained in Contribution Workflow Example.

In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.

@JeffryMAC
Copy link

I think it would be good to add unit test to check both cases (one with dag aware time zone and one without) to make sure this behavior won't be broken in the future

@22quinn 22quinn force-pushed the time-sensor-timezone-aware-dags branch from 61e1815 to 1945da5 Compare July 20, 2020 14:56
@22quinn 22quinn changed the title TimeSensor should consider timezone-aware DAGs TimeSensor should respect DAG timezone Jul 20, 2020
@kaxil kaxil merged commit 9c518fe into apache:master Jul 20, 2020
@22quinn 22quinn deleted the time-sensor-timezone-aware-dags branch July 20, 2020 16:23
@kaxil kaxil added this to the Airflow 1.10.13 milestone Aug 26, 2020
kaxil pushed a commit that referenced this pull request Nov 20, 2020
cfei18 pushed a commit to cfei18/incubator-airflow that referenced this pull request Mar 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants