github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-14 03:46:23 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Heatmap loads forever + Repository list fails to load entirely #4928

New Issue
Closed
opened 2025-11-02 06:07:50 -06:00 by GiteaMirror · 13 comments
GiteaMirror commented 2025-11-02 06:07:50 -06:00
Owner
Copy Link

Originally created by @theAkito on GitHub (Feb 24, 2020).

  • Gitea version (or commit ref): c97433d07
  • Git version: 2.20.1
  • Operating system:
Component Version
Kernel 4.19.0-8-amd64 x86_64
Distro Debian GNU/Linux 10 (buster)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:
    All good.

Description

Web Console

TypeError: Illegal constructor. index.js:2429:20
    e index.js:2429
    c runtime.js:45
    _invoke runtime.js:271
    t runtime.js:97
    n asyncToGenerator.js:3
    s asyncToGenerator.js:25
    exports asyncToGenerator.js:32
    exports asyncToGenerator.js:21
    jQuery 2
        l
        c
Service worker event waitUntil() was passed a promise that rejected with 'TypeError: Cache got basic response with bad status 404 while trying to add request https://domain.tld/js/clipboard.js'. serviceworker.js:52:8

Screenshots

Gitea-error_20200224

Originally created by @theAkito on GitHub (Feb 24, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): c97433d07 - Git version: 2.20.1 - Operating system: Component | Version -- | -- Kernel | 4.19.0-8-amd64 x86_64 Distro | Debian GNU/Linux 10 (buster) - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: All good. ## Description * Heatmap and repository list does not load, at all. * Restarting Gitea or anything like that did not work. * Error occured after upgrading from 68e4f4efc to c97433d07. * Unrelated to https://github.com/go-gitea/gitea/issues/8673. ### Web Console ``` TypeError: Illegal constructor. index.js:2429:20 e index.js:2429 c runtime.js:45 _invoke runtime.js:271 t runtime.js:97 n asyncToGenerator.js:3 s asyncToGenerator.js:25 exports asyncToGenerator.js:32 exports asyncToGenerator.js:21 jQuery 2 l c Service worker event waitUntil() was passed a promise that rejected with 'TypeError: Cache got basic response with bad status 404 while trying to add request https://domain.tld/js/clipboard.js'. serviceworker.js:52:8 ``` ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** --> ![Gitea-error_20200224](https://user-images.githubusercontent.com/26848976/75156844-41505400-5713-11ea-8e21-0a8e7dd73daf.png)
GiteaMirror added the type/question label 2025-11-02 06:07:50 -06:00
GiteaMirror commented 2025-11-02 06:07:51 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Feb 24, 2020):

Have you tried forcing a cache reload? Or un-registering the serviceworker and letting it re-install?

@jolheiser commented on GitHub (Feb 24, 2020): Have you tried forcing a cache reload? Or un-registering the serviceworker and letting it re-install?
GiteaMirror commented 2025-11-02 06:07:51 -06:00
Author
Owner
Copy Link

@theAkito commented on GitHub (Feb 24, 2020):

@jolheiser
No, did not try that, yet. How would I go about doing that?

Meanwhile, I got the old binary back and use this one in the new installation and all is back to normal, as long as this issue ain't fixed, yet.

@theAkito commented on GitHub (Feb 24, 2020): @jolheiser No, did not try that, yet. How would I go about doing that? Meanwhile, I got the old binary back and use this one in the new installation and all is back to normal, as long as this issue ain't fixed, yet.
GiteaMirror commented 2025-11-02 06:07:52 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Feb 24, 2020):

Was this built from source? Does public/js/clipboard.js exist in your source checkout?

@silverwind commented on GitHub (Feb 24, 2020): Was this built from source? Does `public/js/clipboard.js` exist in your source checkout?
GiteaMirror commented 2025-11-02 06:07:52 -06:00
Author
Owner
Copy Link

@theAkito commented on GitHub (Feb 24, 2020):

@silverwind

Yes. I have an update.sh that I use to update Gitea successfully since more than a year. It fetches the newest sources, gets dependencies, etc. then it builds everything from source.

Does public/js/clipboard.js exist in your source checkout?

Yes.

@theAkito commented on GitHub (Feb 24, 2020): @silverwind Yes. I have an `update.sh` that I use to update Gitea successfully since more than a year. It fetches the newest sources, gets dependencies, etc. then it builds everything from source. > Does `public/js/clipboard.js` exist in your source checkout? Yes.
GiteaMirror commented 2025-11-02 06:07:53 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Feb 24, 2020):

Try starting up once with ui.USE_SERVICE_WORKER = false, open the page and then with true again, this should unregister/re-register the service worker.

There is a underlying bug somewhere, but I wonder if SW re-registration helps any or if the error is persistent.

@silverwind commented on GitHub (Feb 24, 2020): Try starting up once with `ui.USE_SERVICE_WORKER = false`, open the page and then with `true` again, this should unregister/re-register the service worker. There is a underlying bug somewhere, but I wonder if SW re-registration helps any or if the error is persistent.
GiteaMirror commented 2025-11-02 06:07:53 -06:00
Author
Owner
Copy Link

@theAkito commented on GitHub (Feb 24, 2020):

@silverwind

Well, turns out, that I changed my update.sh script and forgot to add a go get ... line. I updated most of the dependencies and stuff works now. Thanks everyone.

That said, I encounter 2 other errors when trying to fetch dependencies using go get...:

  1. https://github.com/go-kit/kit/issues/940
  2. https://github.com/influxdata/influxdb/issues/16901

I wasn't able to fix No2, because I don't know which mod/depedency depends on influxdb as a mod/depedency. Therefore I can't fiddle with the go.mod, etc. I just know the most basic stuff about Go, so maybe someone of the more experienced people here could easily solve this.

@theAkito commented on GitHub (Feb 24, 2020): @silverwind Well, turns out, that I changed my `update.sh` script and forgot to add a `go get ...` line. I updated most of the dependencies and stuff works now. Thanks everyone. That said, I encounter 2 other errors when trying to fetch dependencies using `go get...`: 1. https://github.com/go-kit/kit/issues/940 2. https://github.com/influxdata/influxdb/issues/16901 I wasn't able to fix No2, because I don't know which mod/depedency depends on [influxdb](https://github.com/influxdata/influxdb ) as a mod/depedency. Therefore I can't fiddle with the `go.mod`, etc. I just know the most basic stuff about Go, so maybe someone of the more experienced people here could easily solve this.
GiteaMirror commented 2025-11-02 06:07:54 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Feb 24, 2020):

Weird that go dependencies would cause JS errors, I don't believe it. Maybe your build was just unclean. Regarding go modules, I don't think you actually need to go get as we vendor them all inside the repo currently.

@silverwind commented on GitHub (Feb 24, 2020): Weird that go dependencies would cause JS errors, I don't believe it. Maybe your build was just unclean. Regarding go modules, I don't think you actually need to `go get` as we vendor them all inside the repo currently.
GiteaMirror commented 2025-11-02 06:07:54 -06:00
Author
Owner
Copy Link

@theAkito commented on GitHub (Feb 24, 2020):

@silverwind

So the go get ... is redundant?

Maybe your build was just unclean.

Certainly cannot guarantee it wasn't, however it never caused any remarkable issue, like this one.
That said, if it was unclean, it's probably still unclean, as I didn't change the folder or anything like that. All I did was:

  1. go get ... 'ing around
  2. re-building the binary, after inability to fix the influxdb issue
  3. re-running the newly created binary

So, at least it appears to be connected to dependencies, though I wouldn't know how to confirm it.

@theAkito commented on GitHub (Feb 24, 2020): @silverwind So the `go get ...` is redundant? > Maybe your build was just unclean. Certainly cannot guarantee it wasn't, however it never caused any remarkable issue, like this one. That said, if it was unclean, it's probably still unclean, as I didn't change the folder or anything like that. All I did was: 1. go get ... 'ing around 2. re-building the binary, after inability to fix the `influxdb` issue 3. re-running the newly created binary So, at least it appears to be connected to dependencies, though I wouldn't know how to confirm it.
GiteaMirror commented 2025-11-02 06:07:54 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Feb 24, 2020):

Regarding cleaning: Running make clean-all should get you absolutely clean minus node_modules which you can optionally delete too, so rm -rf node_modules && TAGS=bindata make clean-all build should suffice.

I'm no expert on go build, but I've been building without any go get a long time now.

@silverwind commented on GitHub (Feb 24, 2020): Regarding cleaning: Running `make clean-all` should get you absolutely clean minus `node_modules` which you can optionally delete too, so `rm -rf node_modules && TAGS=bindata make clean-all build` should suffice. I'm no expert on go build, but I've been building without any `go get` a long time now.
GiteaMirror commented 2025-11-02 06:07:54 -06:00
Author
Owner
Copy Link

@theAkito commented on GitHub (Feb 24, 2020):

@silverwind

I've been building without any go get a long time now.

Same here. I just didn't know about the vendoring possibility.

Regarding cleaning: Running make clean-all should get you absolutely clean minus node_modules which you can optionally delete too, so rm -rf node_modules && TAGS=bindata make clean-all build should suffice.

Should this be run before every new build?

@theAkito commented on GitHub (Feb 24, 2020): @silverwind > I've been building without any `go get` a long time now. Same here. I just didn't know about the vendoring possibility. > Regarding cleaning: Running `make clean-all` should get you absolutely clean minus `node_modules` which you can optionally delete too, so `rm -rf node_modules && TAGS=bindata make clean-all build` should suffice. Should this be run before every new build?
GiteaMirror commented 2025-11-02 06:07:55 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Feb 24, 2020):

Ideally, our make process should figure out what needs rebuilding but to avoid any potential bugs in that complex process, it never hurts to clean-all. Build will of course take a minute or two longer.

@silverwind commented on GitHub (Feb 24, 2020): Ideally, our `make` process should figure out what needs rebuilding but to avoid any potential bugs in that complex process, it never hurts to `clean-all`. Build will of course take a minute or two longer.
GiteaMirror commented 2025-11-02 06:07:55 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Feb 25, 2020):

Please close if resolved.

@silverwind commented on GitHub (Feb 25, 2020): Please close if resolved.
GiteaMirror commented 2025-11-02 06:07:56 -06:00
Author
Owner
Copy Link

@theAkito commented on GitHub (Feb 25, 2020):

Big thank you to everyone involved in helping!

@theAkito commented on GitHub (Feb 25, 2020): Big thank you to everyone involved in helping!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#4928
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?