gitea serv to enable partial clones with ssh #9832

Closed
opened 2025-11-02 08:50:46 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @panicking on GitHub (Nov 13, 2022).

Description

Ubuntu 22.04 lts

GIT_TRACE=1 git clone --filter=tree:0 ssh://gitea@gitea:38745/common/kernel.git
15:58:08.342028 git.c:455 trace: built-in: git clone --filter=tree:0 ssh://gitea@gitea:38745/common/kernel.git
Cloning into 'kernel'...
15:58:08.348827 run-command.c:668 trace: run_command: unset GIT_DIR; GIT_PROTOCOL=version=2 ssh -o SendEnv=GIT_PROTOCOL -p 38745 gitea@gitea.amarulasolutions.com 'git-upload-pack '''/common/kernel.git''''
warning: filtering not recognized by server, ignoring

Gitea processo during clone

CGroup: /system.slice/gitea.service
         ├─4093562 /opt/gitea/gitea web
         ├─4093737 /usr/bin/git -c protocol.version=2 -c uploadpack.allowfilter=true -c uploadpack.allowAnySHA1InWant=true -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filte>
         ├─4093738 /usr/bin/git -c protocol.version=2 -c uploadpack.allowfilter=true -c uploadpack.allowAnySHA1InWant=true -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filte>
         ├─4093739 /usr/bin/git -c protocol.version=2 -c uploadpack.allowfilter=true -c uploadpack.allowAnySHA1InWant=true -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filte>
         └─4093740 /usr/bin/git -c protocol.version=2 -c uploadpack.allowfilter=true

Gitea Version

1.17.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.25.1, Wire Protocol Version 2 Enabled

Operating System

ubuntu 22.04 LTS

How are you running Gitea?

gitea is official run from systemd on kvm machine not docker

Database

PostgreSQL

Originally created by @panicking on GitHub (Nov 13, 2022). ### Description Ubuntu 22.04 lts GIT_TRACE=1 git clone --filter=tree:0 ssh://gitea@gitea:38745/common/kernel.git 15:58:08.342028 git.c:455 trace: built-in: git clone --filter=tree:0 ssh://gitea@gitea:38745/common/kernel.git Cloning into 'kernel'... 15:58:08.348827 run-command.c:668 trace: run_command: unset GIT_DIR; GIT_PROTOCOL=version=2 ssh -o SendEnv=GIT_PROTOCOL -p 38745 gitea@gitea.amarulasolutions.com 'git-upload-pack '\''/common/kernel.git'\''' warning: filtering not recognized by server, ignoring Gitea processo during clone CGroup: /system.slice/gitea.service ├─4093562 /opt/gitea/gitea web ├─4093737 /usr/bin/git -c protocol.version=2 -c uploadpack.allowfilter=true -c uploadpack.allowAnySHA1InWant=true -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filte> ├─4093738 /usr/bin/git -c protocol.version=2 -c uploadpack.allowfilter=true -c uploadpack.allowAnySHA1InWant=true -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filte> ├─4093739 /usr/bin/git -c protocol.version=2 -c uploadpack.allowfilter=true -c uploadpack.allowAnySHA1InWant=true -c credential.helper= -c filter.lfs.required= -c filter.lfs.smudge= -c filte> └─4093740 /usr/bin/git -c protocol.version=2 -c uploadpack.allowfilter=true ### Gitea Version 1.17.3 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.25.1, Wire Protocol Version 2 Enabled ### Operating System ubuntu 22.04 LTS ### How are you running Gitea? gitea is official run from systemd on kvm machine not docker ### Database PostgreSQL
GiteaMirror added the type/bug label 2025-11-02 08:50:46 -06:00
Author
Owner

@zeripath commented on GitHub (Nov 13, 2022):

Works for me on 1.18-rc0 and dev.

@zeripath commented on GitHub (Nov 13, 2022): Works for me on 1.18-rc0 and dev.
Author
Owner

@zeripath commented on GitHub (Nov 13, 2022):

OK I've been able to replicate on 1.17.3 docker. This is odd.

@zeripath commented on GitHub (Nov 13, 2022): OK I've been able to replicate on 1.17.3 docker. This is odd.
Author
Owner

@zeripath commented on GitHub (Nov 13, 2022):

Aha! I've discovered the issue. The backport was broken.

@zeripath commented on GitHub (Nov 13, 2022): Aha! I've discovered the issue. The backport was broken.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#9832