Activity pages (besides Pulse) seem to no longer work about gitea HOT 14 CLOSED

No issues for me too, in light and dark themes.

@kemzeb , may it be issue with database sync or custom theme?
Admin-Maintenance-> click on all sync operations.

there is no issue with your example

Is there something special with your browser ? Errors in console, etc

from gitea.

Alright working on this 👍

from gitea.

It works for me. 0f3e717

from gitea.

After doing the following:

• Made my fork up-to-date with gitea's main
• Built the project with: TAGS="bindata sqlite sqlite_unlock_notify" make build
• Created a new Gitea repository where I snatched all the commits in a project with 736 commits and merged their main onto mine
• Navigated to the Contributors page
• Disabled my browser cache and reloaded the page

I still have the problem:

The x-axis appears to be correct, but I am not seeing any chart data. I also realized that I'm not seeing any contributor graphs. I'm running on a chromium-based browser. I also checked Firefox and Safari (i.e. I'm using MacOS v14.4.1) and encountered the same problem. Not sure what's going on on my end.

Looking for more examples, I encountered the terraform-provider-gitea project where I also see the issue.

from gitea.

It works for me both chrome and firefox web browser in macOS.

from gitea.

No console or network errors, I still see the the JSON responses are successful; I used Safari, Brave, and Firefox and I don't see anything. I also went on a separate Windows machine with Firefox and I still don't see any chart data. I have used both light and dark themes for each browser.

from gitea.

I have read the PR that introduced this change and my best guess so far has to do with some problem associated to date and time handling (I'm from the US).

from gitea.

Update: it looks like I am right. I changed my operating system to use a European date and time and I can now see the chart data. I'll see if I can make a patch for this (not a frontend wizard but I have read some of the code last night)!

from gitea.

will this be in 1.22.1 or will it stay broken till 1.23.0 for stable users?
because I can reproduce it on my Instance running 1.22.0

from gitea.

We backported this patch, so it should be included in v1.22.0.

I have done the following:

• Removed my previous database directory so that it can be rebuilt
• git checkout v1.22.0
• TAGS="bindata sqlite sqlite_unlock_notify" make build
• ./gitea web
• Created a repository and made 3 commits

And haven't been able to reproduce.

I went to your instance to see if I can gather any useful insights and that's where I noticed that the backend is sending negative Unix times. Here is an example I extracted from inspecting the HTTP responses:

. . .
    "total": {
        "name": "Total",
        "login": "",
        "avatar_link": "",
        "home_link": "",
        "total_commits": 246,
        "weeks": {
            "-62135596800000": {
                "week": -62135596800000,
                "additions": 214923,
                "deletions": 191599,
                "commits": 246
            }
        }
    }
. . .

It doesn't make sense to be getting negative Unix times since they represent times before the Unix epoch.

Given these results, I believe that this is a problem in the backend and we should maybe create a bug report for this.

from gitea.

okay?

anything I can do to help debugging rn?

from gitea.

Side Information: I did the upgrade to 22 just 3 days ago, so I should have the bugfix already, right?

So I guess, I have a weird bug in thte backend, though I would exspect server and not go binary releated

from gitea.

Side Information: I did the upgrade to 22 just 3 days ago, so I should have the bugfix already, right?

Yes, v1.22.0 should have it.

So I guess, I have a weird bug in thte backend, though I would exspect server and not go binary releated

After looking at the code that builds these Unix times, I haven't been able to determine the cause (or if the problem resides elsewhere). If you wish, you can open a new issue so that we can track this potential bug.

from gitea.

Side Information: I did the upgrade to 22 just 3 days ago, so I should have the bugfix already, right?

Yes, v1.22.0 should have it.

So I guess, I have a weird bug in thte backend, though I would exspect server and not go binary releated

After looking at the code that builds these Unix times, I haven't been able to determine the cause (or if the problem resides elsewhere). If you wish, you can open a new issue so that we can track this potential bug.

I just opend up #31248

from gitea.