Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

History charts not showing or loading in v2.15.0 #3114

Closed
cedric-kany opened this issue Dec 13, 2024 · 6 comments
Closed

History charts not showing or loading in v2.15.0 #3114

cedric-kany opened this issue Dec 13, 2024 · 6 comments
Labels
bug Something isn't working fixed in dev Fixed in the dev branch

Comments

@cedric-kany
Copy link

Describe the Bug

The history chart of views and visitors is not showing in the new version of umami, neither in the dashboard nor in the details page. I have multiple pages connected to umami all having the same issue, there are no errors in the console or the requests and the "non-chart" data is showing fine. There might be an issue in the chart library?

image

Database

MySQL

Relevant log output

No response

Which Umami version are you using? (if relevant)

v2.15.0

Which browser are you using? (if relevant)

Chrome (& Arc), Safari Desktop and mobile

How are you deploying your application? (if relevant)

selfhosted next.js

@diarpu
Copy link

diarpu commented Dec 13, 2024

Same here. Also nothing is shown in the realtime graphs, compare.

@tbkblues
Copy link

Same issue here. Seeing this error in log:
Dec 13 11:15:12 www mariadbd[808]: 2024-12-13 11:15:12 20284 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255). Dec 13 11:17:01 www CRON[31254]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

@Bertigrad
Copy link

Same issue here. happened after v2.15.0 update

@mikecao mikecao added the bug Something isn't working label Dec 13, 2024
@Maxime-J
Copy link
Contributor

Hi !
I didn't try that much, but spotted an issue which can surely be the culprit here:

In lib/prisma.ts, MySQL convert_tz expects a timezone to be in a +00:00 like format, which was correctly done with moment-timezone library.
It has changed in the transition to date-fns-tz => tz is now a 'full' date, and should cause NULL values to be returned because it's an invalid argument.

@mikecao mikecao added the fixed in dev Fixed in the dev branch label Dec 15, 2024
@mikecao
Copy link
Collaborator

mikecao commented Dec 15, 2024

Should be fixed in v2.15.1.

@Bertigrad
Copy link

Bertigrad commented Dec 15, 2024

Should be fixed in v2.15.1.

It has been fixed for me in v2.15.1

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working fixed in dev Fixed in the dev branch
Projects
None yet
Development

No branches or pull requests

6 participants