Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Git LFS uploads are broken on try.gitea.io #22194

Closed
kousu opened this issue Dec 21, 2022 · 1 comment
Closed

Git LFS uploads are broken on try.gitea.io #22194

kousu opened this issue Dec 21, 2022 · 1 comment
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@kousu
Copy link
Contributor

kousu commented Dec 21, 2022

Description

The current deployment on try.gitea.io doesn't seem to accept any LFS uploads. It fails with

batch request: Gitea: Unknown git command: exit status 1

or

batch response: Repository or object not found: https://try.gitea.io/$USER/$REPO.git/info/lfs/objects/batch

So, something to do with batch requests?

The logs I have are short, hopefully it's okay if I inline them:

SSH
$ cd $(mktemp -d)
$ mkdir test && cd test
$ git init
Initialized empty Git repository in /tmp/tmp.GCTMQXLKfx/test/.git/
$ git checkout -b main
Switched to a new branch 'main'
$ git lfs install
Updated Git hooks.
Git LFS initialized.
$ git lfs track "*.md"
Tracking "*.md"
$ echo '# Testing READMEs in LFS' > README.md
$ echo '# Testing documents in LFS' > CONTRIBUTING.md
$ git add .
$ git commit -m "first commit"
$ git remote add origin git@try.gitea.io:kousu1/test-lfs-rendering.git
[main (root-commit) a869fdc] first commit
 3 files changed, 7 insertions(+)
 create mode 100644 .gitattributes
 create mode 100644 CONTRIBUTING.md
 create mode 100644 README.md
$ git push -u origin main
The authenticity of host 'try.gitea.io (167.99.148.217)' can't be established.
ED25519 key fingerprint is SHA256:mDBx/XdOw4ZLaq0JKQXVy6SpXuGOoeHheyBdFH9W9ig.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'try.gitea.io' (ED25519) to the list of known hosts.
Remote "origin" does not support the Git LFS locking API. Consider disabling it with:
  $ git config lfs.https://try.gitea.io/kousu1/test-lfs-rendering.git/info/lfs.locksverify false
batch request: Gitea: Unknown git command: exit status 1                                                                                              
error: failed to push some refs to 'try.gitea.io:kousu1/test-lfs-rendering.git'
HTTP
$ cd $(mktemp -d)
$ mkdir test && cd test
$ git init
Initialized empty Git repository in /tmp/tmp.iVv7CorWbY/test/.git/
$ git checkout -b main
Switched to a new branch 'main'
$ git lfs install
Git LFS initialized.
Updated Git hooks.
$ git lfs track "*.md"
Tracking "*.md"
$ echo '# Testing READMEs in LFS' > README.md
$ echo '# Testing documents in LFS' > CONTRIBUTING.md
$ git add .
$ git commit -m "first commit"
[main (root-commit) 394c712] first commit
 3 files changed, 7 insertions(+)
 create mode 100644 .gitattributes
 create mode 100644 CONTRIBUTING.md
 create mode 100644 README.md
$ git remote add origin https://try.gitea.io/kousu1/test-lfs-rendering.git
$ git push -u origin main
Username for 'https://try.gitea.io': kousu1
Password for 'https://kousu1@try.gitea.io': 
batch response: Repository or object not found: https://try.gitea.io/kousu1/test-lfs-rendering.git/info/lfs/objects/batch                             
Check that it exists and that you have proper access to it
error: failed to push some refs to 'https://try.gitea.io/kousu1/test-lfs-rendering.git'

If I build and run locally, at the current HEAD (70d15e7), I get version 1.19.0+dev-173-g68704532c, but I cannot reproduce locally.

Gitea Version

1.19.0+dev-207-g70d15e778

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?

try.gitea.io

Database

None

@lunny
Copy link
Member

lunny commented May 9, 2023

I think this is because try site has a limited disk so LFS has been disabled.

@lunny lunny closed this as completed May 9, 2023
@lunny lunny added type/question Issue needs no code to be fixed, only a description on how to fix it yourself. and removed type/bug labels May 9, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

2 participants