github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-26 04:50:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

MigratePost: Clone: signal: killed #1208

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

Originally created by @husky2017 on GitHub (Nov 4, 2017).

  • Gitea version (or commit ref): 1.2.2
  • Git version: git version 1.8.3.1
  • Operating system: Centos 3.10.0-693.el7.x86_64 && 8G DDR3 I3-4160
  • 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:

2017/11/04 14:22:29 [...routers/repo/repo.go:107 handleCreateError()] [E] MigratePost: Clone: signal: killed

Description

Migration: https://github.com/torvalds/linux.git

Get error..

help me, thank you !!
...

Screenshots

Originally created by @husky2017 on GitHub (Nov 4, 2017). <!-- 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.2.2 - Git version: git version 1.8.3.1 - Operating system: Centos 3.10.0-693.el7.x86_64 && 8G DDR3 I3-4160 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: 2017/11/04 14:22:29 [...routers/repo/repo.go:107 handleCreateError()] [E] MigratePost: Clone: signal: killed ## Description Migration: https://github.com/torvalds/linux.git Get error.. help me, thank you !! ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/bug label 2025-11-02 03:52:29 -06:00
GiteaMirror commented 2025-11-02 03:52:30 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Nov 4, 2017):

Most probably migration needs to be made asynchronous otherwise for large repositories it can timeout

@lafriks commented on GitHub (Nov 4, 2017): Most probably migration needs to be made asynchronous otherwise for large repositories it can timeout
GiteaMirror commented 2025-11-02 03:52:30 -06:00
Author
Owner
Copy Link

@husky2017 commented on GitHub (Nov 4, 2017):

Mr.lafriks, thank you。visiting GitHub is very slow in China, so i need cache something。

@husky2017 commented on GitHub (Nov 4, 2017): Mr.lafriks, thank you。visiting GitHub is very slow in China, so i need cache something。
GiteaMirror commented 2025-11-02 03:52:30 -06:00
Author
Owner
Copy Link

@hetykai commented on GitHub (May 15, 2018):

Is there a solution?

@hetykai commented on GitHub (May 15, 2018): Is there a solution?
GiteaMirror commented 2025-11-02 03:52:30 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (May 15, 2018):

You can increase migration and mirroring timeout times in app.ini. Even if page times out migrations/mirroring will continue to run in background.

[git.timeout]
MIGRATE = 600
MIRROR = 300
@lafriks commented on GitHub (May 15, 2018): You can increase migration and mirroring timeout times in app.ini. Even if page times out migrations/mirroring will continue to run in background. ``` [git.timeout] MIGRATE = 600 MIRROR = 300 ```
GiteaMirror commented 2025-11-02 03:52:31 -06:00
Author
Owner
Copy Link

@hetykai commented on GitHub (May 16, 2018):

@lafriks Thank you, it looks like a good solution, I'll try it.

@hetykai commented on GitHub (May 16, 2018): @lafriks Thank you, it looks like a good solution, I'll try it.
GiteaMirror commented 2025-11-02 03:52:31 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 26, 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 (Jan 26, 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 03:52:31 -06:00
Author
Owner
Copy Link

@davidak commented on GitHub (Jan 26, 2019):

Does it solve the problem for you, @husky2017 @hetykai?

Then it can get documented at https://docs.gitea.io/en-us/troubleshooting/

And maybe configure it that way on demo instance.

@davidak commented on GitHub (Jan 26, 2019): Does it solve the problem for you, @husky2017 @hetykai? Then it can get documented at https://docs.gitea.io/en-us/troubleshooting/ And maybe configure it that way on demo instance.
GiteaMirror commented 2025-11-02 03:52:31 -06:00
Author
Owner
Copy Link

@hetykai commented on GitHub (Jan 27, 2019):

Does it solve the problem for you, @husky2017 @hetykai?

Then it can get documented at https://docs.gitea.io/en-us/troubleshooting/

And maybe configure it that way on demo instance.

Yes, it works for me.

@hetykai commented on GitHub (Jan 27, 2019): > Does it solve the problem for you, @husky2017 @hetykai? > > Then it can get documented at https://docs.gitea.io/en-us/troubleshooting/ > > And maybe configure it that way on demo instance. Yes, it works for me.
GiteaMirror commented 2025-11-02 03:52:31 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 7, 2019):

Please feel free to reopen it.

@lunny commented on GitHub (Feb 7, 2019): Please feel free to reopen it.
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#1208
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?