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

Monitoring page fails - probably during a problem with an unavailable source for mirrored repositories #1791

New Issue
Closed
opened 2025-11-02 04:13:20 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 04:13:20 -06:00
Owner
Copy Link

Originally created by @SlavekB on GitHub (May 16, 2018).

  • Gitea version (or commit ref): 1.4.1
  • Git version: 2.1.4
  • Operating system: Debian GNU/Linux 8.x
  • 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

In my instance of Gitea I have several mirrors of GIT repositories. However, the source server of these mirrors is now unavailable for some time.

Screenshots

System Notices are properly reported about failure of mirror synchronization:

Failed to update mirror repository...

But Monitoring page now fails:

template: admin/monitor:52:19: executing "admin/monitor" at <.Start.FormatLong>: can't evaluate field FormatLong in type time.Time

Originally created by @SlavekB on GitHub (May 16, 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.4.1 - Git version: 2.1.4 - Operating system: Debian GNU/Linux 8.x - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description In my instance of Gitea I have several mirrors of GIT repositories. However, the source server of these mirrors is now unavailable for some time. ## Screenshots System Notices are properly reported about failure of mirror synchronization: > Failed to update mirror repository... But Monitoring page now fails: > template: admin/monitor:52:19: executing "admin/monitor" at <.Start.FormatLong>: can't evaluate field FormatLong in type time.Time <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/bug label 2025-11-02 04:13:20 -06:00
GiteaMirror commented 2025-11-02 04:13:21 -06:00
Author
Owner
Copy Link

@SlavekB commented on GitHub (May 18, 2018):

I can confirm that when the source server for mirrors is available, Monitoring page is working again.

@SlavekB commented on GitHub (May 18, 2018): I can confirm that when the source server for mirrors is available, Monitoring page is working again.
GiteaMirror commented 2025-11-02 04:13:21 -06:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 31, 2018):

I think it's caused by this PR #3142

@ghost commented on GitHub (May 31, 2018): I think it's caused by this PR #3142
GiteaMirror commented 2025-11-02 04:13:21 -06:00
Author
Owner
Copy Link

@daviian commented on GitHub (Jun 9, 2018):

@SlavekB @yasuokav Are you able to verify that the PR fixes that issue?

@daviian commented on GitHub (Jun 9, 2018): @SlavekB @yasuokav Are you able to verify that the PR fixes that issue?
GiteaMirror commented 2025-11-02 04:13:21 -06:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 10, 2018):

@daviian Yes, it works for me now.

@ghost commented on GitHub (Jun 10, 2018): @daviian Yes, it works for me now.
GiteaMirror commented 2025-11-02 04:13:21 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jun 10, 2018):

closed by #4203

@lunny commented on GitHub (Jun 10, 2018): closed by #4203
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#1791
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?