Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Heatmap Rendering broken #5328

Closed
2 of 7 tasks
Cellebyte opened this issue Nov 13, 2018 · 3 comments · Fixed by #5511
Closed
2 of 7 tasks

Heatmap Rendering broken #5328

Cellebyte opened this issue Nov 13, 2018 · 3 comments · Fixed by #5511
Labels

Comments

@Cellebyte
Copy link

Cellebyte commented Nov 13, 2018

  • Gitea version (or commit ref): 1.6.0+rc1-105-g4c1f1f964 (ref: 4c1f1f9)
  • Git version: Alpine git
  • Operating system: Alpine Linux
  • 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:

Description

build a docker image from the master today which is integrated with our MsSQL Database.

The database schema is Latin1_General_CI_AI.

The return code is 500 "Internal Server Error".

Do we use the wrong schema?

{
    "message":"arg timestamp as int: strconv.ParseInt: parsing \"2018-11-13T00:00:00Z\": invalid syntax",
    "url":"https://godoc.org/github.com/go-gitea/go-sdk/gitea"
}

Screenshots

screenshot from 2018-11-13 16-03-51

@lunny
Copy link
Member

lunny commented Nov 29, 2018

It should also be fixed by #5401

@lunny lunny closed this as completed Nov 29, 2018
@Cellebyte
Copy link
Author

It should also be fixed by #5401

Will their be a backport to 1.6 or will it be released in 1.7?

@lafriks
Copy link
Member

lafriks commented Nov 29, 2018

Heatmap is not part of 1.6.0 release

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants