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

Duplicated feed for new repos #5503

New Issue
Closed
opened 2025-11-02 06:26:52 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 06:26:52 -06:00
Owner
Copy Link

Originally created by @ozonep on GitHub (Jun 5, 2020).

  • Gitea version (or commit ref): 1.11.0-rc1 and later
  • Git version: not relevant
  • Operating system: 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

I faced an issue.
Every time I create new repo it appears twice in my feed + it's counted as 2 contributions instead of 1.
Although new commits appear correctly in feed, as 1 entry.
After testing all versions I can say that this bug appeared for the first time in v1.11.0-rc1.
On 1.10.6 everything's fine.
Also tried dev version from "master" branch - the bug is still there.

Running in Kubernetes + also tested locally running official Docker container (with default settings).

Screenshots

ivan - Dashboard - Gitea: Git with a cup of tea 2020-06-05 15-44-14

Originally created by @ozonep on GitHub (Jun 5, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) 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.11.0-rc1 and later - Git version: not relevant - Operating system: Linux - Database (use `[x]`): - [x] PostgreSQL - [x] MySQL - [x] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description I faced an issue. Every time I create new repo it appears twice in my feed + it's counted as 2 contributions instead of 1. Although new commits appear correctly in feed, as 1 entry. After testing all versions I can say that this bug appeared for the first time in v1.11.0-rc1. On 1.10.6 everything's fine. Also tried dev version from "master" branch - the bug is still there. Running in Kubernetes + also tested locally running official Docker container (with default settings). ## Screenshots ![ivan - Dashboard - Gitea: Git with a cup of tea 2020-06-05 15-44-14](https://user-images.githubusercontent.com/20884214/83878022-25ae0e00-a744-11ea-93a6-b56d37f5ecbe.png)
GiteaMirror added the issue/stale label 2025-11-02 06:26:52 -06:00
GiteaMirror commented 2025-11-02 06:26:53 -06:00
Author
Owner
Copy Link

@ozonep commented on GitHub (Jun 9, 2020):

I found root cause of that issue.
It happens after initial install (with setting configuration options), and is fixed after first reboot of the server.
I see 2 options here:

  • Add to Docs that server should be rebooted not only after upgrade but after clean install too.
  • Add
    ctx.Redirect(form.AppURL)
    graceful.GetManager().DoGracefulRestart()
    at the end of 'install.go' script... To force-restart service....
@ozonep commented on GitHub (Jun 9, 2020): I found root cause of that issue. It happens after initial install (with setting configuration options), and is fixed after first reboot of the server. I see 2 options here: - Add to Docs that server should be rebooted not only after upgrade but after clean install too. - Add `ctx.Redirect(form.AppURL)` `graceful.GetManager().DoGracefulRestart()` at the end of 'install.go' script... To force-restart service....
GiteaMirror commented 2025-11-02 06:26:53 -06:00
Author
Owner
Copy Link

@ozonep commented on GitHub (Jun 9, 2020):

The main issue here is that usually with Docker install you don't stop your service once it's started, (until/unless you update image version).
So I'd never guessed to just restart container or Kubernetes pod...

@ozonep commented on GitHub (Jun 9, 2020): The main issue here is that usually with Docker install you don't stop your service once it's started, (until/unless you update image version). So I'd never guessed to just restart container or Kubernetes pod...
GiteaMirror commented 2025-11-02 06:26:53 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Aug 8, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Aug 8, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
GiteaMirror commented 2025-11-02 06:26:53 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Sep 2, 2020):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Sep 2, 2020): This issue has been automatically closed because of inactivity. You can re-open it if needed.
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
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#5503
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?