github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-10 22:06:34 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Incorrect Time is displayed when check the Submit time #3720

New Issue
Closed
opened 2025-11-02 05:22:57 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 05:22:57 -06:00
Owner
Copy Link

Originally created by @suli3 on GitHub (Aug 3, 2019).

  • Gitea version (or commit ref): 1.9.0 docker
  • Git version:
  • Operating system: Centos
  • 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

The submit time is about 1 o'clock.
The Check time is about 2 o'clock.

The submit time description is right which is an hour ago,
but the Exact moment should be about 1 o'clock on the morning of August 3, but now is about 15:21 of August 3 . . .

But where the wrong submit time come from?
I noticed that issue #7239 maybe the same problem or a very similar problem ...

Screenshots

48RIZELJ}K)O`75{ER}H$PB

I hv checked the time in the docker and the server time, there are the same.
QSHAP9R379L}68VS`)K9 MP

Originally created by @suli3 on GitHub (Aug 3, 2019). - Gitea version (or commit ref): 1.9.0 docker - Git version: - Operating system: Centos - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description The submit time is about 1 o'clock. The Check time is about 2 o'clock. The submit time description is right which is an hour ago, but the Exact moment should be about 1 o'clock on the morning of August 3, but now is about 15:21 of August 3 . . . But where the wrong submit time come from? I noticed that issue #7239 maybe the same problem or a very similar problem ... ## Screenshots ![48RIZELJ}K)O`75{ER}H$PB](https://user-images.githubusercontent.com/1057425/62407004-04d8d180-b5e4-11e9-8a82-14ac6cc98254.png) I hv checked the time in the docker and the server time, there are the same. ![QSHAP9R379L}68VS`)K9 MP](https://user-images.githubusercontent.com/1057425/62407006-099d8580-b5e4-11e9-9c35-8ea3bb77c4a3.png) <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/staletype/bug labels 2025-11-02 05:22:57 -06:00
GiteaMirror commented 2025-11-02 05:22:57 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Oct 2, 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 (Oct 2, 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:22:58 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Oct 2, 2019):

Should be closed by #7792

@lunny commented on GitHub (Oct 2, 2019): Should be closed by #7792
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/stale 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#3720
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?