JS error on action run page #27213
Comments
|
Could you provide more detailed information in the Chrome dev console about where the error occurs? |
|
Need a stack trace and/or screenshot of surrounding code in devtools. You will need to check "Preserve Log" in the devtools console so it persists across page reload: 
BTW I fixed a similar bug in #26985, but I think this one is different. |
|
That's everything I get. Do you have any other suggestions how to narrow it down? |
|
Click on the index.js link top right, then find the button to pretty-print the source and screenshot that. From the stack trace I can see it happens in |
|
|
|
Oops, yes that should have a return. The error message is odd but I'm pretty sure the return will fix it and this is the effect of a network error you are seeing where the return value of those fetches is undefined because it threw. Not sure if I will be able to reproduce the exact error you had. |
Backport #27289 by @silverwind Should fix: #27213 @denyskon can you test this? I can not reproduce this error locally. Co-authored-by: silverwind <me@silverwind.io>
Previously, the production build never output sourcemaps. Now we emit one file for `index.js` because it is the most likely one where we need to be able to better debug reported issues like #27213. This will currently increase the binary size of gitea by around 700kB which is what the gzipped source map file has. Also, I fixed the CSS sourcemap generation which was broken since the introduction of lightningcss.
…tea#27291) Previously, the production build never output sourcemaps. Now we emit one file for `index.js` because it is the most likely one where we need to be able to better debug reported issues like go-gitea#27213. This will currently increase the binary size of gitea by around 700kB which is what the gzipped source map file has. Also, I fixed the CSS sourcemap generation which was broken since the introduction of lightningcss.
… (#27295) Backport #27291 by @silverwind Previously, the production build never output sourcemaps. Now we emit one file for `index.js` because it is the most likely one where we need to be able to better debug reported issues like #27213. This will currently increase the binary size of gitea by around 700kB which is what the gzipped source map file has. Also, I fixed the CSS sourcemap generation which was broken since the introduction of lightningcss. The chinese docs are machine-translated, please correct accordingly. Co-authored-by: silverwind <me@silverwind.io>
Description
Bildschirmaufzeichnung.vom.2023-09-23.17-34-22.webm
Switching from an action run page to another page, an error appears saying
JavaScript promise rejection: TypeError: t is undefinedGitea Version
1.21.0-rc0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Docker-Compose
Database
SQLite
The text was updated successfully, but these errors were encountered: