SamWheating edited a comment on issue #17906: URL: https://github.com/apache/airflow/issues/17906#issuecomment-909719331
This comes down to the intended behaviour of [moment-timezone](https://github.com/moment/moment-timezone), the JS package used for handling timezones in the UI. Here's the part of the source which populates that field: https://github.com/apache/airflow/blob/dd386c81f50fe2a93cf0bff0c3da2c66f2dc6e6a/airflow/www/static/js/datetime_utils.js#L23-L33 You can replicate this behaviour by running the relevant line of code in the javascript console of the Airflow webserver: ```javascript > moment().tz("America/Vancouver").format('z (Z)') "PDT (-07:00)" > moment().tz("Chile/Continental").format('z (Z)') "-04 (-04:00)" ``` Looking into the discussion in [this issue](https://github.com/moment/moment-timezone/issues/841) on moment-timezone, I believe that this is intended behaviour for some timezones due to this [ICANN change from 2017](https://mm.icann.org/pipermail/tz-announce/2017-February/000045.html) in which it was decided to use numeric abbreviations for many South American time zones. So in short, I don't think that this issue is something that can be reasonably fixed within Airflow. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
