github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Issue due dates not exported in gitea dump #3872

New Issue
Open
opened 2025-11-02 05:29:05 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 05:29:05 -06:00
Owner
Copy Link

Originally created by @PerfectSlayer on GitHub (Aug 29, 2019).

  • Gitea version (or commit ref): 1.8.2
  • Git version: 2.17.1
  • Operating system: CentOS
  • Database:
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

When dumping a backup, the issue due dates in SQL dump are not valid.
The problem is the field deadline_unix of the table issue.
All the exported values equal -62135596800 if a due date is set, 0 otherwise.

0 is fine but negative value for a timestamp is wrong.
Once reimported, the due date show is the 1st of January 1970.

Screenshots

image
image

Originally created by @PerfectSlayer on GitHub (Aug 29, 2019). - Gitea version (or commit ref): 1.8.2 - Git version: 2.17.1 - Operating system: CentOS - Database: - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description When dumping a backup, the issue due dates in SQL dump are not valid. The problem is the field `deadline_unix` of the table `issue`. All the exported values equal `-62135596800` if a due date is set, `0` otherwise. `0` is fine but negative value for a timestamp is wrong. Once reimported, the due date show is the 1st of January 1970. ## Screenshots ![image](https://user-images.githubusercontent.com/1766222/63943650-691a7400-ca70-11e9-850e-ed1fcdceb338.png) ![image](https://user-images.githubusercontent.com/1766222/63943772-9bc46c80-ca70-11e9-9f42-a4db95af0491.png)
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 05:29:06 -06:00
GiteaMirror commented 2025-11-02 05:29:06 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Aug 29, 2019):

@lunny Could this be upstream xorm issue?

@lafriks commented on GitHub (Aug 29, 2019): @lunny Could this be upstream xorm issue?
GiteaMirror commented 2025-11-02 05:29:06 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Sep 15, 2019):

I will take a look at this.

@lunny commented on GitHub (Sep 15, 2019): I will take a look at this.
GiteaMirror commented 2025-11-02 05:29:06 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Nov 14, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Nov 14, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 05:29:07 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Mar 22, 2024):

Maybe we need a validate for deadline.
2f060c5834/routers/web/repo/issue.go (L2303-L2309)

@yp05327 commented on GitHub (Mar 22, 2024): Maybe we need a validate for deadline. https://github.com/go-gitea/gitea/blob/2f060c5834d81f0317c795fc281f9a07e03e5962/routers/web/repo/issue.go#L2303-L2309
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 issue/confirmed 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#3872
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?