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

packet fatal: early EOF fatal #13439

New Issue
Closed
opened 2025-11-02 10:42:23 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 10:42:23 -06:00
Owner
Copy Link

Originally created by @nfalperen on GitHub (Aug 29, 2024).

Description

There are serious problems with the application. It stubbornly gives errors when trying to clone many repositories. Sometimes errors occur after the repository is completely downloaded. The error is as follows:

https://github.com/keras-team/keras konumundan taşıma başarısız oldu.

migration failed: clone error: exit status 128 - error: RPC failed; curl 56 Recv failure: Connection reset by peer error: 4246 bytes of body are still expected fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output

After making the git config --global http.postBuffer 1048576000 and git config --global http.version HTTP/1.1 settings, this time it gave an error like the one below.

https://github.com/tensorflow/tensorflow konumundan taşıma başarısız oldu.

migration failed: clone timed out, consider increasing [git.timeout] MIGRATE in app.ini, underlying err: context deadline exceeded - fatal: early EOF

It works completely on its own. Sometimes, when I clone a repository that I couldn't one day, it gets cloned in the evening or the next day. I can't understand why it gives these errors. How do software developers working on huge repositories do this?
If it is useful for this issue, some log entries are as follows:

gitea | 2024/08/29 20:58:26 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/task/25 for 192.168.0.164:51348, 200 OK in 1.7ms @ user/task.go:16(user.TaskStatus)
gitea | 2024/08/29 20:58:28 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/task/25 for 192.168.0.164:51349, 200 OK in 1.6ms @ user/task.go:16(user.TaskStatus)
gitea | 2024/08/29 20:58:29 ...eb/routing/logger.go:68:func1() [I] router: polling GET /user/events for 192.168.0.164:51348, elapsed 3618.4ms @ events/events.go:18(events.Events)
gitea | 2024/08/29 20:58:30 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/task/25 for 192.168.0.164:51349, 200 OK in 2.0ms @ user/task.go:16(user.TaskStatus)
gitea | 2024/08/29 20:58:32 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/task/25 for 192.168.0.164:51349, 200 OK in 2.0ms @ user/task.go:16(user.TaskStatus)
gitea | 2024/08/29 20:58:34 ...ices/task/migrate.go:60:func1() [E] runMigrateTask[25] by DoerID[1] to RepoID[26] for OwnerID[1] failed: migration failed: clone error: exit status 128 - error: RPC failed; curl 56 Recv failure: Connection reset by peer
gitea | error: 4246 bytes of body are still expected
gitea | fetch-pack: unexpected disconnect while reading sideband packet
gitea | fatal: early EOF
gitea | fatal: fetch-pack: invalid index-pack output
gitea | 2024/08/29 20:58:34 ...ervices/task/task.go:53:handler() [E] Run task failed: migration failed: clone error: exit status 128 - error: RPC failed; curl 56 Recv failure: Connection reset by peer
gitea | error: 4246 bytes of body are still expected
gitea | fetch-pack: unexpected disconnect while reading sideband packet
gitea | fatal: early EOF
gitea | fatal: fetch-pack: invalid index-pack output
gitea | 2024/08/29 20:58:34 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/task/25 for 192.168.0.164:51349, 200 OK in 1.3ms @ user/task.go:16(user.TaskStatus)
gitea | 2024/08/29 21:04:19 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for 192.168.0.164:51348, 200 OK in 353097.9ms @ events/events.go:18(events.Events)
gitea | 2024/08/29 21:04:19 ...eb/routing/logger.go:102:func1() [I] router: completed GET /wfwqcflh for 192.168.0.164:51520, 200 OK in 42.8ms @ user/home.go:713(user.UsernameSubRoute)
gitea | 2024/08/29 21:04:19 ...eb/routing/logger.go:102:func1() [I] router: completed GET /avatar/a2bd80402723b9c5ff6f27d9cddc1911?size=512 for 192.168.0.164:51520, 303 See Other in 183.7ms @ user/avatar.go:48(user.AvatarByEmailHash)
gitea | 2024/08/29 21:04:19 ...eb/routing/logger.go:102:func1() [I] router: completed GET /avatar/a2bd80402723b9c5ff6f27d9cddc1911?size=48 for 192.168.0.164:51521, 303 See Other in 144.6ms @ user/avatar.go:48(user.AvatarByEmailHash)
gitea | 2024/08/29 21:04:21 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for 192.168.0.164:51521, 200 OK in 1606.3ms @ events/events.go:18(events.Events)
gitea | 2024/08/29 21:04:21 ...eb/routing/logger.go:102:func1() [I] router: completed GET /wfwqcflh/tensorflow for 192.168.0.164:51523, 200 OK in 7.7ms @ repo/view.go:774(repo.Home)
gitea | 2024/08/29 21:04:21 ...eb/routing/logger.go:102:func1() [I] router: completed GET /avatar/a2bd80402723b9c5ff6f27d9cddc1911?size=48 for 192.168.0.164:51523, 303 See Other in 22.6ms @ user/avatar.go:48(user.AvatarByEmailHash)
gitea | 2024/08/29 21:04:21 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/task/24 for 192.168.0.164:51523, 200 OK in 1.8ms @ user/task.go:16(user.TaskStatus)
gitea | 2024/08/29 21:04:24 ...eb/routing/logger.go:68:func1() [I] router: polling GET /user/events for 192.168.0.164:51523, elapsed 3025.2ms @ events/events.go:18(events.Events)

Gitea Version

1.22.1

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

I installed CasaOS 0.41 on Raspberry Pi OS 64 bit operating system on Raspberry Pi 5. I installed and ran Gitea with this CasaOS.

Database

SQLite

Originally created by @nfalperen on GitHub (Aug 29, 2024). ### Description There are serious problems with the application. It stubbornly gives errors when trying to clone many repositories. Sometimes errors occur after the repository is completely downloaded. The error is as follows: https://github.com/keras-team/keras konumundan taşıma başarısız oldu. migration failed: clone error: exit status 128 - error: RPC failed; curl 56 Recv failure: Connection reset by peer error: 4246 bytes of body are still expected fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output After making the git config --global http.postBuffer 1048576000 and git config --global http.version HTTP/1.1 settings, this time it gave an error like the one below. https://github.com/tensorflow/tensorflow konumundan taşıma başarısız oldu. migration failed: clone timed out, consider increasing [git.timeout] MIGRATE in app.ini, underlying err: context deadline exceeded - fatal: early EOF It works completely on its own. Sometimes, when I clone a repository that I couldn't one day, it gets cloned in the evening or the next day. I can't understand why it gives these errors. How do software developers working on huge repositories do this? If it is useful for this issue, some log entries are as follows: gitea | 2024/08/29 20:58:26 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/task/25 for 192.168.0.164:51348, 200 OK in 1.7ms @ user/task.go:16(user.TaskStatus) gitea | 2024/08/29 20:58:28 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/task/25 for 192.168.0.164:51349, 200 OK in 1.6ms @ user/task.go:16(user.TaskStatus) gitea | 2024/08/29 20:58:29 ...eb/routing/logger.go:68:func1() [I] router: polling GET /user/events for 192.168.0.164:51348, elapsed 3618.4ms @ events/events.go:18(events.Events) gitea | 2024/08/29 20:58:30 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/task/25 for 192.168.0.164:51349, 200 OK in 2.0ms @ user/task.go:16(user.TaskStatus) gitea | 2024/08/29 20:58:32 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/task/25 for 192.168.0.164:51349, 200 OK in 2.0ms @ user/task.go:16(user.TaskStatus) gitea | 2024/08/29 20:58:34 ...ices/task/migrate.go:60:func1() [E] runMigrateTask[25] by DoerID[1] to RepoID[26] for OwnerID[1] failed: migration failed: clone error: exit status 128 - error: RPC failed; curl 56 Recv failure: Connection reset by peer gitea | error: 4246 bytes of body are still expected gitea | fetch-pack: unexpected disconnect while reading sideband packet gitea | fatal: early EOF gitea | fatal: fetch-pack: invalid index-pack output gitea | 2024/08/29 20:58:34 ...ervices/task/task.go:53:handler() [E] Run task failed: migration failed: clone error: exit status 128 - error: RPC failed; curl 56 Recv failure: Connection reset by peer gitea | error: 4246 bytes of body are still expected gitea | fetch-pack: unexpected disconnect while reading sideband packet gitea | fatal: early EOF gitea | fatal: fetch-pack: invalid index-pack output gitea | 2024/08/29 20:58:34 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/task/25 for 192.168.0.164:51349, 200 OK in 1.3ms @ user/task.go:16(user.TaskStatus) gitea | 2024/08/29 21:04:19 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for 192.168.0.164:51348, 200 OK in 353097.9ms @ events/events.go:18(events.Events) gitea | 2024/08/29 21:04:19 ...eb/routing/logger.go:102:func1() [I] router: completed GET /wfwqcflh for 192.168.0.164:51520, 200 OK in 42.8ms @ user/home.go:713(user.UsernameSubRoute) gitea | 2024/08/29 21:04:19 ...eb/routing/logger.go:102:func1() [I] router: completed GET /avatar/a2bd80402723b9c5ff6f27d9cddc1911?size=512 for 192.168.0.164:51520, 303 See Other in 183.7ms @ user/avatar.go:48(user.AvatarByEmailHash) gitea | 2024/08/29 21:04:19 ...eb/routing/logger.go:102:func1() [I] router: completed GET /avatar/a2bd80402723b9c5ff6f27d9cddc1911?size=48 for 192.168.0.164:51521, 303 See Other in 144.6ms @ user/avatar.go:48(user.AvatarByEmailHash) gitea | 2024/08/29 21:04:21 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for 192.168.0.164:51521, 200 OK in 1606.3ms @ events/events.go:18(events.Events) gitea | 2024/08/29 21:04:21 ...eb/routing/logger.go:102:func1() [I] router: completed GET /wfwqcflh/tensorflow for 192.168.0.164:51523, 200 OK in 7.7ms @ repo/view.go:774(repo.Home) gitea | 2024/08/29 21:04:21 ...eb/routing/logger.go:102:func1() [I] router: completed GET /avatar/a2bd80402723b9c5ff6f27d9cddc1911?size=48 for 192.168.0.164:51523, 303 See Other in 22.6ms @ user/avatar.go:48(user.AvatarByEmailHash) gitea | 2024/08/29 21:04:21 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/task/24 for 192.168.0.164:51523, 200 OK in 1.8ms @ user/task.go:16(user.TaskStatus) gitea | 2024/08/29 21:04:24 ...eb/routing/logger.go:68:func1() [I] router: polling GET /user/events for 192.168.0.164:51523, elapsed 3025.2ms @ events/events.go:18(events.Events) ### Gitea Version 1.22.1 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? I installed CasaOS 0.41 on Raspberry Pi OS 64 bit operating system on Raspberry Pi 5. I installed and ran Gitea with this CasaOS. ### Database SQLite
GiteaMirror added the issue/needs-feedback label 2025-11-02 10:42:23 -06:00
GiteaMirror commented 2025-11-02 10:42:24 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 29, 2024):

I believe this is your network problem. I cannot reproduce it on the demo site. Ref https://demo.gitea.com/lunny/keras and https://demo.gitea.com/lunny/tensorflow

@lunny commented on GitHub (Aug 29, 2024): I believe this is your network problem. I cannot reproduce it on the demo site. Ref https://demo.gitea.com/lunny/keras and https://demo.gitea.com/lunny/tensorflow
GiteaMirror commented 2025-11-02 10:42:24 -06:00
Author
Owner
Copy Link

@nfalperen commented on GitHub (Sep 8, 2024):

Hello, there may be a problem with the network. But it may not be only related to the network. Because I have now connected my Raspberry directly to a more powerful and new modem with a cable. This time it said that my repository could not be cloned because "github does not allow it". In other words, for some reason that I cannot understand, GitHub does not allow me to review some projects. Thank you for your help.

@nfalperen commented on GitHub (Sep 8, 2024): Hello, there may be a problem with the network. But it may not be only related to the network. Because I have now connected my Raspberry directly to a more powerful and new modem with a cable. This time it said that my repository could not be cloned because "github does not allow it". In other words, for some reason that I cannot understand, GitHub does not allow me to review some projects. Thank you for your help.
GiteaMirror commented 2025-11-02 10:42:24 -06:00
Author
Owner
Copy Link

@nfalperen commented on GitHub (Sep 11, 2024):

Connecting to a newer Router allowed me to clone keras and tensorflow. But I still get an error like below when trying to clone the https://github.com/torvalds/linux repository.

https://github.com/torvalds/linux konumundan taşıma başarısız oldu.

migration failed: clone timed out, consider increasing [git.timeout] MIGRATE in app.ini, underlying err: context deadline exceeded - fatal: early EOF

I don't think it's a network issue. If it was, I have a lot of devices connected to the network. Some of them would be giving network-related errors.
The storage completes the download process, downloads 5 - 6 GB of data, and when the storage is completely downloaded, it gives an error and deletes the entire storage.

When I install git-scm software on my computer and do the same cloning process, I get the same error. Or I get other errors similar to this error. The problem may not be with Gitea. There are many solutions on the internet about the solution to the error, but none of them correctly identify the source of the problem and are successful solutions by chance. Generally, solutions are "it worked when I did this". When I do it that way, it still doesn't work.

@nfalperen commented on GitHub (Sep 11, 2024): Connecting to a newer Router allowed me to clone keras and tensorflow. But I still get an error like below when trying to clone the https://github.com/torvalds/linux repository. https://github.com/torvalds/linux konumundan taşıma başarısız oldu. migration failed: clone timed out, consider increasing [git.timeout] MIGRATE in app.ini, underlying err: context deadline exceeded - fatal: early EOF I don't think it's a network issue. If it was, I have a lot of devices connected to the network. Some of them would be giving network-related errors. The storage completes the download process, downloads 5 - 6 GB of data, and when the storage is completely downloaded, it gives an error and deletes the entire storage. When I install git-scm software on my computer and do the same cloning process, I get the same error. Or I get other errors similar to this error. The problem may not be with Gitea. There are many solutions on the internet about the solution to the error, but none of them correctly identify the source of the problem and are successful solutions by chance. Generally, solutions are "it worked when I did this". When I do it that way, it still doesn't work.
GiteaMirror commented 2025-11-02 10:42:25 -06:00
Author
Owner
Copy Link

@GiteaBot commented on GitHub (Oct 11, 2024):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Oct 11, 2024): We close issues that need feedback from the author if there were no new comments for a month. :tea:
GiteaMirror commented 2025-11-02 10:42:25 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Oct 11, 2024):

You can change the [git.timeout] to a bigger number.

@lunny commented on GitHub (Oct 11, 2024): You can change the `[git.timeout]` to a bigger number.
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/needs-feedback
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#13439
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?