User action heatmap

[kolaente]

This pr adds heatmaps to user's profile, just like the ones on github or gitlab. It takes every action from the action table to build the grid, this means things like issue comments are also included, not only code commits. The fetching is done via a new api endpoint.
I also added a config option to globally disable this.

With some tests, it does not seem like this is something which draws a lot performance (takes ~0.005 sec on a prod gitea server), so I see no reason to implement extra caching.

@markuman I saw your example and tried to re-use some things frontend wise, but unfortualy, the code is minified, so I couldn't use it. Feel free to comment if you have some ideas on how to improve the frontend code, js is not my strength.

Closes #6 and #4918

Screenshot

[codecov-io]

Codecov Report

Merging #5131 into master will increase coverage by 0.04%.
The diff coverage is 70.31%.

@@            Coverage Diff             @@
##           master    #5131      +/-   ##
==========================================
+ Coverage   37.44%   37.48%   +0.04%     
==========================================
  Files         308      309       +1     
  Lines       45718    45782      +64     
==========================================
+ Hits        17119    17162      +43     
- Misses      26141    26159      +18     
- Partials     2458     2461       +3

Impacted Files	Coverage Δ
modules/setting/setting.go	48.24% <100%> (+0.06%)	⬆️
routers/user/profile.go	33.03% <100%> (+0.61%)	⬆️
routers/user/home.go	41.98% <100%> (+0.34%)	⬆️
models/unit_tests.go	72.8% <100%> (+0.24%)	⬆️
routers/api/v1/api.go	74.84% <33.33%> (-0.54%)	⬇️
routers/api/v1/user/user.go	23.52% <66.66%> (+13.82%)	⬆️
models/user_heatmap.go	78.94% <78.94%> (ø)
models/repo_list.go	62.2% <0%> (-1.17%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f38fce9...e8a7559. Read the comment docs.

[lafriks]

I don't think we need special setting to enable/disable this

[techknowlogick]

I like the option of enable/disable as not everyone wants this and it can cause load on the database.

On Sat, Oct 20, 2018, at 2:55 PM, Lauris BH wrote: I don't think we need special setting to enable/disable this — You are receiving this because you commented. Reply to this email directly, view it on GitHub[1], or mute the thread[2].

Links: 1. #5131 (comment) 2. https://github.com/notifications/unsubscribe-auth/AAKBZR89lcfo_vi6tAnx0o02tfjIB95rks5um3G8gaJpZM4XyB2I

[kolaente]

@lafriks @techknowlogick I also thought this can make massive load on the database, which is why I implemented the setting. I also did some benchmarks and discovered the mariadb caching on this itself is already very good (After the query was executed a few times, it takes 0.000 sec to get the results. This probably will be different when executed on a very large installation of Gitea. Maybe someone could test the query on try.gitea.io?

@lafriks As I already implemented it and set it to on by default, I don't think there's a need to remove the setting. If it still bothers someon, they can disable it.

[nicolafio]

@kolaente Second one looks super, though that last green cell is bugging me a bit since it's skewed more on the right, after the end of the grey separation line on the bottom.

Also, how does it behave on small screens such as phones?

Oh, and thanks for your effort, by the way. You're our hero.

[kolaente]

@Jd342 not that good on small screens, as I said it doesn't really scale well.

though that last green cell is bugging me a bit since it's skewed more on the right, after the end of the grey separation line on the bottom.

I think that is a bug in the library we're using to display this... hmmmmm.....

[nicolafio]

@kolaente Is it possible to display only the last month instead of the whole year for that case?

I like your animosity in the last commit of that screenshot.

You might want to get a coffee with some sugar, or some crackers.

[kolaente]

@Jd342

Is it possible to display only the last month instead of the whole year for that case?

I don't think that library can do that.

I like your animosity in the last commit of that screenshot.

That's nothing I wrote, its a git alias which gets a random commit message from http://whatthecommit.com/ - that way I dont need to do `git commit -am "now think of a commit message && git push" every time I test someting. I'm fine, don't worry. (I didn't even recognize the commit message until you pointed it out)

[kolaente]

@kolaente I don't think that library can do that.

Oh it seems like it can. I'll try it.

[adelowo]

@Jd342 not that good on small screens, as I said it doesn't really scale well.

Github disables the heatmap on mobile. That could be an option.

[nicolafio]

@kolaente

I think that is a bug in the library we're using to display this... hmmmmm.....

It's probably just some missing margin/padding, since the same thing happens in the left with the names of the day.

That's nothing I wrote, its a git alias which gets a random commit message from http://whatthecommit.com/ - that way I dont need to do `git commit -am "now think of a commit message && git push" every time I test someting. I'm fine, don't worry. (I didn't even recognize the commit message until you pointed it out)

Gotcha. Do consider the crackers, though. I want you to feel energetic and give your best in this PR. I like productive people, especially when they do work for me for free.

[kolaente]

Github disables the heatmap on mobile. That could be an option.

I've just done that, seems to be the easiest solution.

[nicolafio]

I've just done that, seems to be the easiest solution.

Bummer. It'd have been nice to see it on mobile as well. If it's an issue, I could help out on this - maybe by opening a PR myself after this one.

[kolaente]

Bummer. It'd have been nice to see it on mobile as well. If it's an issue, I could help out on this - maybe by opening a PR myself after this one.

That seems like a good idea, my current priority is to get the heatmap itself merged, we can think about such enhancments later.

[tonysgi]

The heatmap is great. I noticed when I was creating a test on https://try.gitea.com that 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. I was able to replicate on several local copies of Gitea as well. Prob should just show an empty heatmap? Should I submit a bug or is this comment good enough?