Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

New Windows PT time zone results in UI error due to unresolved time zone

Closed Beginner friendly
#75,697 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
66/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

Start in the Airflow web UI code where the selected time zone is resolved and used to render times; the report points to an unguarded selectedTimezone.toUpperCase() call but gives no source file or test. Reproduce with the Windows Pacific Time zone and cleared browser local storage, then find or add a test for an unresolved OS time zone. Done means time-rendering pages load with a safe fallback instead of crashing.

Written by the indexing model from the issue text.

Description

kind:bug needs-triage
Under which category would you file this issue?

Airflow Core

Apache Airflow version

3.1.7

What happened and how to reproduce it?

After recently switching my time zone from PDT to the new unified Pacific Time (PT) time zone, I received the following error after logging in:

TypeError: Cannot read properties of undefined (reading 'toUpperCase')
    at gd (index-DMFz1oOG.js:584:8179)
    at Dft (index-DMFz1oOG.js:70:34718)
    at Jit (index-DMFz1oOG.js:70:63847)
    at Dvn (index-DMFz1oOG.js:70:74419)
    at a1n (index-DMFz1oOG.js:70:108782)
    at fSr (index-DMFz1oOG.js:70:107817)
    at Ttt (index-DMFz1oOG.js:70:107643)
    at r1n (index-DMFz1oOG.js:70:104696)
    at m1n (index-DMFz1oOG.js:70:116348)
    at MessagePort.vn (index-DMFz1oOG.js:55:1683)

This appears to be caused by stale time zone information in local storage and an unguarded call to selectedTimezone.toUpperCase() where selectedTimezone is undefined due to being unable to resolve the OS time zone to an IANA name.

Reproduction:

  1. Set your Windows time zone to Pacific Time (UTC -7:00)
  2. Clear browser local storage for the Airflow server
  3. Log in to Airflow
  4. Any page that renders the Time crashes

I'm able to work around this by changing the time zone for my user in the Airflow UI.

What you think should happen instead?

The UI should fall back to a known value when it fails to resolve the OS time zone, e.g., UTC. Any page that renders the time should not crash.

Operating System

Windows 11 64-bit

Deployment

Official Apache Airflow Helm Chart

Apache Airflow Provider(s)

No response

Versions of Apache Airflow Providers

No response

Official Helm Chart version

Not Applicable

Kubernetes Version

Not Applicable

Helm Chart configuration

No response

Docker Image customizations

No response

Anything else?

No response

Are you willing to submit PR?
  • Yes I am willing to submit a PR!
Code of Conduct
Dominant language
Python
Stars
47.3k
Forks
18.1k
Avg merge
18h 16m
Merged PRs (30d)
647

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/airflow

All issues in apache/airflow

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.