jscheffl opened a new issue, #65715:
URL: https://github.com/apache/airflow/issues/65715

   ### Under which category would you file this issue?
   
   Airflow Core
   
   ### Apache Airflow version
   
   3.2.1
   
   ### What happened and how to reproduce it?
   
   See also discussion in Slack in 
https://apache-airflow.slack.com/archives/C03G9H97MM2/p1776934570392409
   
   We upgraded Airflow from 3.1.7 to 3.2.1 and saw that most of the new 
translation keys were not loaded. Many users reported this as error.
   
   <img width="366" height="162" alt="Image" 
src="https://github.com/user-attachments/assets/64fa5975-37e4-4349-9e24-cd3f9c209926";
 />
   
   In my (personal) case even a SHIFT+Reload in Firefox did not help, I was 
able to fix it only by clearing all browser cache files manually
   Browser: Firefox on Linux
   Might be related to my corporate environment, maybe also some Proxy in the 
chain was caching too aggressive?
   
   ### What you think should happen instead?
   
   If a new UI version is rolled by some means it should be ensured that 
translation files are uploaded fresh. Potentially encoding the core version 
number in the URL path or so.
   
   ### Operating System
   
   Windows and Linux
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Apache Airflow Provider(s)
   
   _No response_
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Official Helm Chart version
   
   1.19.0
   
   ### Kubernetes Version
   
   _No response_
   
   ### 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
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to