-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
JavaScript WARNING/ERROR: JavaScript promise rejection #28226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I get same message for https://github.com/tensorflow/tensorflow |
Please provide enough logs: "Open browser console to see more details" Although there is no enough feedback, I could guess that it's caused by : Copy citation file content, in APA and BibTex format, on repo home page #19999 , the citation-js failed to parse some data in CITATION.cff |
@wxiaoguang as I wrote, it can be reproduced on try.gitea.io. But ... |
They are different problems. The author's problem is caused by #19999 when there is an invalid date in CITATION file. The |
You're right. |
Backport #28433 by wxiaoguang Fix #28226 Co-authored-by: wxiaoguang <[email protected]>
Not the same error message but similar
Disabling Dark Reader extension in Firefox solved the problem. |
Looks like it is fixed in 1.21.4 |
This is likely an external browser store plugin bug, and after I eliminated it, it didn't issue a warning. Gitea1.21.4 |
Automatically locked because of our CONTRIBUTING guidelines |
…itea#28437) Backport go-gitea#28433 by wxiaoguang Fix go-gitea#28226 Co-authored-by: wxiaoguang <[email protected]> (cherry picked from commit 5e2bae7)
Description
I have this https://github.com/run-llama/llama_index mirror in my gitea. And Chrome/FF shows:
On GitHub I can't see this Warning/Error.
Gitea Version
1.21.0
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
2.43.0
Operating System
Ubuntu 22.04.3 LTS x86_64
How are you running Gitea?
gitea-1.21.0-linux-amd64
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: