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

404 when trying to stop the timer which has been started before binary upgrade #10258

New Issue
Closed
opened 2025-11-02 09:02:24 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 09:02:24 -06:00
Owner
Copy Link

Originally created by @bagasme on GitHub (Feb 12, 2023).

Description

I was curious about using timer/stopwatch feature of Gitea. I enabled the timer when the deployed binary version was about 7ae10cb7f1.

Today I build Gitea from version e460b6ef4d and deployed it. When I tried to stop the timer,
Gitea returned 404 on https://%(DOMAIN)s/times/stopwatch/toggle, thus the timer cannot be stopped.

I guessed that commit 90cf07a2c8 touched the subsystem in question.

Gitea Version

main (commit e460b6ef4d)

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

https://gist.github.com/bagasme/335d722c4f87f552176b352d2e466f84

Screenshots

Stopping timer 404

Git Version

2.39.1

Operating System

Ubuntu 22.04

How are you running Gitea?

I built Gitea from source using Go 1.20, Node v18.13.0 (installed via nvm) on Debian 11.

The Gitea instance is hosted on a LXD container on my computer.

Database

PostgreSQL

Originally created by @bagasme on GitHub (Feb 12, 2023). ### Description I was curious about using timer/stopwatch feature of Gitea. I enabled the timer when the deployed binary version was about 7ae10cb7f1a520d46c2c92d60cf5181c3d7b6850. Today I build Gitea from version e460b6ef4da02aa03e7eaa9baa23dbd62898fc44 and deployed it. When I tried to stop the timer, Gitea returned 404 on `https://%(DOMAIN)s/times/stopwatch/toggle`, thus the timer cannot be stopped. I guessed that commit 90cf07a2c8dc2917d0c02648f0a69e0229cfce21 touched the subsystem in question. ### Gitea Version main (commit e460b6ef4da02aa03e7eaa9baa23dbd62898fc44) ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist https://gist.github.com/bagasme/335d722c4f87f552176b352d2e466f84 ### Screenshots ![Stopping timer 404](https://user-images.githubusercontent.com/40219486/218300450-f4d62ce8-aac1-4cdd-9641-0c9b96070cdb.png) ### Git Version 2.39.1 ### Operating System Ubuntu 22.04 ### How are you running Gitea? I built Gitea from source using Go 1.20, Node v18.13.0 (installed via nvm) on Debian 11. The Gitea instance is hosted on a LXD container on my computer. ### Database PostgreSQL
GiteaMirror added the type/bug label 2025-11-02 09:02:24 -06:00
GiteaMirror commented 2025-11-02 09:02:25 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 12, 2023):

The generated stopwatch URL is not ideal, if there is no ActiveStopWatch then it outputs incorrect URL

(Hmm, it seems not related to your problem directly, so just FYI)

image

I just played a while, I think it could be just a display bug? Maybe you do not have active stopwatch yet ..... The display bug is confirmed and is still being fixed .....

Could you help to confirm how your problem happens, especially the screenshots? Is there an active stopwatch?

@wxiaoguang commented on GitHub (Feb 12, 2023): ~~The generated stopwatch URL is not ideal, if there is no ActiveStopWatch then it outputs incorrect URL~~ (Hmm, it seems not related to your problem directly, so just FYI) <details> ![image](https://user-images.githubusercontent.com/2114189/218322243-c4317e74-0954-437d-a285-479008effe04.png) </details> ---- I just played a while, I think it could be just a display bug? Maybe you do not have active stopwatch yet ..... The display bug is confirmed and is still being fixed ..... Could you help to confirm how your problem happens, especially the screenshots? Is there an active stopwatch?
GiteaMirror commented 2025-11-02 09:02:26 -06:00
Author
Owner
Copy Link

@bagasme commented on GitHub (Feb 13, 2023):

Could you help to confirm how your problem happens, especially the screenshots? Is there an active stopwatch?

My Gitea instance have implicit ENABLE_TIMETRACKING=true (as the config item isn't specified in app.ini). When it is set to false, the timer is paused; but when I set it again to true, the timer resumes.

Anyway, how can I check if there is active stopwatches?

@bagasme commented on GitHub (Feb 13, 2023): > Could you help to confirm how your problem happens, especially the screenshots? Is there an active stopwatch? My Gitea instance have implicit `ENABLE_TIMETRACKING=true` (as the config item isn't specified in `app.ini`). When it is set to `false`, the timer is paused; but when I set it again to `true`, the timer resumes. Anyway, how can I check if there is active stopwatches?
GiteaMirror commented 2025-11-02 09:02:26 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 13, 2023):

Screenshots?

ps: the display bug of #22169 problem would be fixed by #22879 -- if 22169 is the cause.

@wxiaoguang commented on GitHub (Feb 13, 2023): Screenshots? ps: the display bug of #22169 problem would be fixed by #22879 -- if 22169 is the cause.
GiteaMirror commented 2025-11-02 09:02:26 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 13, 2023):

Please have a try to see whether 22879 resolve the "display bug" on your side (I guess).

@wxiaoguang commented on GitHub (Feb 13, 2023): Please have a try to see whether 22879 resolve the "display bug" on your side (I guess).
GiteaMirror commented 2025-11-02 09:02:26 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 20, 2023):

I would assume that the problem has been resolved?

@wxiaoguang commented on GitHub (Feb 20, 2023): I would assume that the problem has been resolved?
GiteaMirror commented 2025-11-02 09:02:26 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 28, 2023):

I would assume that the problem has been resolved?

Hmm ... maybe there is no more problem. I guess the problem was the UI regression caused by https://github.com/go-gitea/gitea/pull/22169 , it should have been fixed by https://github.com/go-gitea/gitea/pull/22879

@wxiaoguang commented on GitHub (Feb 28, 2023): > I would assume that the problem has been resolved? Hmm ... maybe there is no more problem. I guess the problem was the UI regression caused by https://github.com/go-gitea/gitea/pull/22169 , it should have been fixed by https://github.com/go-gitea/gitea/pull/22879
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#10258
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?