The locale of "updated" is wrong, if the repo is updated by a user using other custom language
<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label. For the Community Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug For the Enterprise Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary The locale of "updated" is wrong, if the repo is updated by a user using custom language ### Steps to reproduce Having somebody with the chinese locale set push to a project and visit the dashboard afterwards, should appear broken for other members of organization ### Example Project https://gitlab.com/ipzn/ipzn ### What is the current *bug* behavior? Local of "Updated" is the local locale of the user who pushed ### What is the expected *correct* behavior? Locale should ### Relevant logs and/or screenshots ![image](/uploads/f7ec4a5289953b92b1810154b2e0347c/image.png) ### Output of checks This bug happens on GitLab.com #### Results of GitLab environment info - ### Possible fixes It seems to be somewhere in the template caching mechanism. Possibly add the locale of the user to the hash function for generating the cached filename?
issue