github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

As a new user, the heatmap does not render until you have submitted the first commit. #2434

New Issue
Closed
opened 2025-11-02 04:36:00 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 04:36:00 -06:00
Owner
Copy Link

Originally created by @tonysgi on GitHub (Oct 23, 2018).

  • Gitea version (or commit ref): 2ce72d4
  • Git version: 2.15.2
  • Operating system: Linux
  • Database (use [x]):
    • PostgreSQL
    • [x ] MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes - Create a new user to see bug
    • No
    • Not relevant
  • Log gist:

Description

As a new user, the heatmap does not render until you have submitted the first commit. Until that happens, it is perpetually displaying the "heatmap.loading" icon.

Screenshots

image

Originally posted by @tonysgi in https://github.com/go-gitea/gitea/pull/5131#issuecomment-432329383

Originally created by @tonysgi on GitHub (Oct 23, 2018). - Gitea version (or commit ref): 2ce72d4 - Git version: 2.15.2 - Operating system: Linux - Database (use `[x]`): - [ ] PostgreSQL - [x ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes - Create a new user to see bug - [ ] No - [ ] Not relevant - Log gist: ## Description As a new user, the heatmap does not render until you have submitted the first commit. Until that happens, it is perpetually displaying the "heatmap.loading" icon. ## Screenshots ![image](https://user-images.githubusercontent.com/1932681/47377120-703f5b80-d6c2-11e8-9470-96ca1c6a16d1.png) _Originally posted by @tonysgi in https://github.com/go-gitea/gitea/pull/5131#issuecomment-432329383_
GiteaMirror added the type/bug label 2025-11-02 04:36:00 -06:00
GiteaMirror commented 2025-11-02 04:36:01 -06:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 23, 2018):

Normally it shouldn't show "heatmap.loading", there should be a text.

I think it doesn't load because the API returns null if the user has no actions yet, which the js library then fails to parse. I'll submit a patch tomorrow

@kolaente commented on GitHub (Oct 23, 2018): Normally it shouldn't show "heatmap.loading", there should be a text. I think it doesn't load because the API returns `null` if the user has no actions yet, which the js library then fails to parse. I'll submit a patch tomorrow
GiteaMirror commented 2025-11-02 04:36:01 -06:00
Author
Owner
Copy Link

@sapk commented on GitHub (Oct 23, 2018):

@kolaente I already proposed a fix. You are right, it is because the array is not init (in the api reply) and the json representation is null not [].

@sapk commented on GitHub (Oct 23, 2018): @kolaente I already proposed a fix. You are right, it is because the array is not init (in the api reply) and the json representation is `null` not `[]`.
GiteaMirror commented 2025-11-02 04:36:01 -06:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Oct 24, 2018):

@sapk Great! Thanks!

@kolaente commented on GitHub (Oct 24, 2018): @sapk Great! Thanks!
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/bug
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#2434
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?