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

Error in the HTTP2 framing layer #11846

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

Originally created by @somera on GitHub (Oct 13, 2023).

Description

Today I found this

==> servicesmirror-trace.log <==
2023/10/13 21:23:16 ...irror/mirror_pull.go:290:runSync() [E] SyncMirrors [repo: <Repository 17976:solidiquis/erdtree>]: failed to update mirror repository:
Stdout:
Stderr: fatal: unable to access 'https://github.com/solidiquis/erdtree.git/': Error in the HTTP2 framing layer

Err: exit status 128
        /source/services/mirror/mirror_pull.go:290 (0x246377e)
        /source/services/mirror/mirror_pull.go:432 (0x2466187)
        /source/services/mirror/mirror.go:28 (0x245e04e)
        /source/services/mirror/mirror.go:125 (0x245ea24)
        /source/modules/queue/workerqueue.go:246 (0x1c9ecbc)
        /source/modules/queue/workergroup.go:98 (0x1ca14ad)
        /source/modules/queue/workergroup.go:162 (0x1c9e6c8)
        /usr/local/go/src/runtime/asm_amd64.s:1598 (0x472700)
                goexit: BYTE    $0x90   // NOP

22 times in my gitea.log.

Any ide what can be the reason for this?

Gitea Version

1.20.5

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.42.0

Operating System

Ubuntu 20.04.6

How are you running Gitea?

gitea-1.20.5-linux-amd64

Database

PostgreSQL

Originally created by @somera on GitHub (Oct 13, 2023). ### Description Today I found this ``` ==> servicesmirror-trace.log <== 2023/10/13 21:23:16 ...irror/mirror_pull.go:290:runSync() [E] SyncMirrors [repo: <Repository 17976:solidiquis/erdtree>]: failed to update mirror repository: Stdout: Stderr: fatal: unable to access 'https://github.com/solidiquis/erdtree.git/': Error in the HTTP2 framing layer Err: exit status 128 /source/services/mirror/mirror_pull.go:290 (0x246377e) /source/services/mirror/mirror_pull.go:432 (0x2466187) /source/services/mirror/mirror.go:28 (0x245e04e) /source/services/mirror/mirror.go:125 (0x245ea24) /source/modules/queue/workerqueue.go:246 (0x1c9ecbc) /source/modules/queue/workergroup.go:98 (0x1ca14ad) /source/modules/queue/workergroup.go:162 (0x1c9e6c8) /usr/local/go/src/runtime/asm_amd64.s:1598 (0x472700) goexit: BYTE $0x90 // NOP ``` 22 times in my gitea.log. Any ide what can be the reason for this? ### Gitea Version 1.20.5 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.42.0 ### Operating System Ubuntu 20.04.6 ### How are you running Gitea? gitea-1.20.5-linux-amd64 ### Database PostgreSQL
GiteaMirror added the type/bug label 2025-11-02 09:49:33 -06:00
GiteaMirror commented 2025-11-02 09:49:34 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (Oct 14, 2023):

I don't think this is a Gitea problem. Do you have a proxy or something infront of Gitea which could mess up the connection?

@KN4CK3R commented on GitHub (Oct 14, 2023): I don't think this is a Gitea problem. Do you have a proxy or something infront of Gitea which could mess up the connection?
GiteaMirror commented 2025-11-02 09:49:34 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Oct 14, 2023):

There is no prxy. I see this since two days. But not for every mirrorr update. And this is random. And I don't have any connections issues. Or this is an gitHub problem. I try to analyze it.

@somera commented on GitHub (Oct 14, 2023): There is no prxy. I see this since two days. But not for every mirrorr update. And this is random. And I don't have any connections issues. Or this is an gitHub problem. I try to analyze it.
GiteaMirror commented 2025-11-02 09:49:34 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Oct 14, 2023):

I can't reproduce it or GitHub fixed this.

@somera commented on GitHub (Oct 14, 2023): I can't reproduce it or GitHub fixed this.
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#11846
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?