github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-17 06:32:41 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Double activity entry #4848

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

Originally created by @vanvanni on GitHub (Feb 13, 2020).

  • Gitea version (or commit ref): V1.11.0
  • Git version: 2.17.1
  • Operating system: Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-76-generic x86_64)
  • 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

Creation of a repo has a double activity entry

Screenshots

image

Originally created by @vanvanni on GitHub (Feb 13, 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): V1.11.0 - Git version: 2.17.1 - Operating system: Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-76-generic x86_64) - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ## Description Creation of a repo has a double activity entry ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** --> ![image](https://user-images.githubusercontent.com/13612647/74476344-6e963a00-4ea9-11ea-8ef1-7a6665ab31f6.png)
GiteaMirror added the issue/stale label 2025-11-02 06:04:51 -06:00
GiteaMirror commented 2025-11-02 06:04:52 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Feb 13, 2020):

I cannot re-create this on try or with a fresh 1.11.0 build.

Can you provide logs if there is anything of interest?
As well, how are you creating the repositories? Just the web UI?

For two actions to be pushed to the DB at the same time, it's almost like there's more than one instance of Gitea running, though I'm not sure how they would both overlap without some error.

@jolheiser commented on GitHub (Feb 13, 2020): I cannot re-create this on try or with a fresh `1.11.0` build. Can you provide logs if there is anything of interest? As well, how are you creating the repositories? Just the web UI? For two actions to be pushed to the DB at the same time, it's almost like there's more than one instance of Gitea running, though I'm not sure how they would both overlap without some error.
GiteaMirror commented 2025-11-02 06:04:52 -06:00
Author
Owner
Copy Link

@vanvanni commented on GitHub (Feb 13, 2020):

I cannot re-create this on try or with a fresh 1.11.0 build.

Can you provide logs if there is anything of interest?
As well, how are you creating the repositories? Just the web UI?

For two actions to be pushed to the DB at the same time, it's almost like there's more than one instance of Gitea running, though I'm not sure how they would both overlap without some error.

I have searched the logs but they where cleared since I was playing with log rotation, have my server has been rebooted it has been solved. I cannot trace the cause. I will keep track of this and post when it occurs again

@vanvanni commented on GitHub (Feb 13, 2020): > I cannot re-create this on try or with a fresh `1.11.0` build. > > Can you provide logs if there is anything of interest? > As well, how are you creating the repositories? Just the web UI? > > For two actions to be pushed to the DB at the same time, it's almost like there's more than one instance of Gitea running, though I'm not sure how they would both overlap without some error. I have searched the logs but they where cleared since I was playing with log rotation, have my server has been rebooted it has been solved. I cannot trace the cause. I will keep track of this and post when it occurs again
GiteaMirror commented 2025-11-02 06:04:52 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Apr 13, 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 (Apr 13, 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:04:52 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Apr 28, 2020):

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

@stale[bot] commented on GitHub (Apr 28, 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#4848
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?