github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-14 11:56:41 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Heatmap Rendering broken #2525

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

Originally created by @Cellebyte on GitHub (Nov 13, 2018).

  • Gitea version (or commit ref): 1.6.0+rc1-105-g4c1f1f964 (ref: 4c1f1f9646)
  • 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

Originally created by @Cellebyte on GitHub (Nov 13, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.6.0+rc1-105-g4c1f1f964 (ref: 4c1f1f96465e809161f7d634a07eb60b4511db35) - Git version: Alpine git - Operating system: Alpine Linux - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [x] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] 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? ```json { "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 <!-- **If this issue involves the Web Interface, please include a screenshot** --> ![screenshot from 2018-11-13 16-03-51](https://user-images.githubusercontent.com/16540824/48421929-ccdfe480-e75d-11e8-9c87-b51d3719a641.png)
GiteaMirror added the type/bug label 2025-11-02 04:39:27 -06:00
GiteaMirror commented 2025-11-02 04:39:28 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Nov 29, 2018):

It should also be fixed by #5401

@lunny commented on GitHub (Nov 29, 2018): It should also be fixed by #5401
GiteaMirror commented 2025-11-02 04:39:28 -06:00
Author
Owner
Copy Link

@Cellebyte commented on GitHub (Nov 29, 2018):

It should also be fixed by #5401

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

@Cellebyte commented on GitHub (Nov 29, 2018): > It should also be fixed by #5401 Will their be a backport to 1.6 or will it be released in 1.7?
GiteaMirror commented 2025-11-02 04:39:28 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Nov 29, 2018):

Heatmap is not part of 1.6.0 release

@lafriks commented on GitHub (Nov 29, 2018): Heatmap is not part of 1.6.0 release
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#2525
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?