Getting JS "ChunkLoadError" when visiting issue after upgrading.

[chriseaton]

• Gitea version (or commit ref): v1.13.0
• Git version: 2.26.2
• Operating system: CentOS 8, 3.10.0-1160.6.1.el7.x86_64 Binary release downloaded.
  Google Chrome v87.0.4280.88 (Official Build) (64-bit)
• Database (use [x]):
  • [x] PostgreSQL
  • [ ] MySQL
  • [ ] MSSQL
  • [ ] SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • [ ] Yes (provide example URL)
  • [x] No
• Log gist: No server indication of error, that I can tell:

  Dec 16 16:51:28 bananas-server gitea[14835]: [Macaron] [Static] Serving /js/index.js.map
  Dec 16 16:51:28 bananas-server gitea[14835]: [Macaron] 2020-12-16 16:51:28: Completed GET /js/index.js.map 200 OK in 28.561937ms
  Dec 16 16:51:28 bananas-server gitea[14835]: [Macaron] 2020-12-16 16:51:28: Started GET /manifest.json for 192.168.1.65
  Dec 16 16:51:28 bananas-server gitea[14835]: [Macaron] 2020-12-16 16:51:28: Started GET /img/favicon.png for 192.168.1.65
  Dec 16 16:51:28 bananas-server gitea[14835]: [Macaron] [Static] Serving /img/favicon.png
  Dec 16 16:51:28 bananas-server gitea[14835]: [Macaron] 2020-12-16 16:51:28: Completed GET /img/favicon.png 200 OK in 144.251µs
  Dec 16 16:51:28 bananas-server gitea[14835]: [Macaron] 2020-12-16 16:51:28: Completed GET /manifest.json 200 OK in 2.373734ms
  Dec 16 16:51:30 bananas-server gitea[14835]: [Macaron] 2020-12-16 16:51:30: Started GET /serviceworker.js for 192.168.1.65
  Dec 16 16:51:30 bananas-server gitea[14835]: [Macaron] [Static] Serving /serviceworker.js
  Dec 16 16:51:30 bananas-server gitea[14835]: [Macaron] 2020-12-16 16:51:30: Completed GET /serviceworker.js 304 Not Modified in 99.126µs

  Description

  1. Upgraded from v1.12.3 to v1.13.0 by shuting down and updating the binary release. Startup went well (server log above).
  2. Went to a project's issue detail screen (eg /proof-of-concept/some-repo/issues/3) noticed buttons weren't working correctly. Checked javascript console and have:

     bootstrap:151 Uncaught ChunkLoadError: Loading chunk 2 failed.
     (missing: https://bananas-server/js/dropzone.js)
     at Function.a.e (https://bananas-server/js/index.js?v=a4729905ff114b8772756edddf6ef3f4:1:1724)
     at https://bananas-server/js/index.js?v=a4729905ff114b8772756edddf6ef3f4:1:827491
     at u (https://bananas-server/js/index.js?v=a4729905ff114b8772756edddf6ef3f4:1:10712)
     at Generator._invoke (https://bananas-server/js/index.js?v=a4729905ff114b8772756edddf6ef3f4:1:10500)
     at Generator.next (https://bananas-server/js/index.js?v=a4729905ff114b8772756edddf6ef3f4:1:11137)
     at n (https://bananas-server/js/index.js?v=a4729905ff114b8772756edddf6ef3f4:1:4774)
     at s (https://bananas-server/js/index.js?v=a4729905ff114b8772756edddf6ef3f4:1:4985)
     at https://bananas-server/js/index.js?v=a4729905ff114b8772756edddf6ef3f4:1:5044
     at new Promise (<anonymous>)
     at https://bananas-server/js/index.js?v=a4729905ff114b8772756edddf6ef3f4:1:4925

  3. Cleared all application data, cache, etc. Disabled ad-blocker, same result. Nothing in server logs.
  4. Error appears on load of the issue (details) page only. Other pages do not have an error. ...

Screenshots

[chriseaton]

Nevermind - figured it out. For some reason after the upgrade, and even after clearing the application cache Chrome still held onto the offline files. Not sure why. I resolved it by explicitly right-clicking an offline request in the Network tab, and saying "Clear browser cache." it had to be on the offline request (with the gear by it), the regular one didn't clear offline data (nor did clear all data in the Application tab). Super wacky. Dammit chrome.