Thanks for the feedback!

How can I reproduce?

I got it like this:

1. Downloaded update 0.12.3
2. Turned off the web server
3. Moved the folders from the old gogs directory to the new
4. Enabled the web server
   ** The site is up, the contents of the repository opens **
5. Made git commit and git push
6. I go to the web server
   ** The site is working, the contents of the repository to which the push was made DO NOT open. Error 500. **
   The rest of the repositories on the same site are opened.

Moved content to old version 0.11.91.
Repository to open again on old version after git push.

Can you provide a sample repo that can cause 0.12.3 to 500?

I will try to update my home repository to version 0.12.3 and report the results. But Linux Mint 20 is installed there, not Debian 10.

But it is visible on the Internet.

I appreciate your replies but I still have no idea how to reproduce the problem. I'll ask this instead, are you able to reproduce the 500 on https://try.gogs.io?

I checked it on my home PC (Linux Mint 20). It was also updated to 0.12.3 and made a push. The repository opens fine. Problem only means Debian 10 or installed packages. I will look for the problem further.

Can you upload a sample repository to try.gogs.io and reproduce the 500?

Unfortunately, I can't. This is a corporate project. The source code cannot be posted on the Internet. And I do not think that this is the case in the project code.

But I can lay out the project structure:

The last commit was added to the following line in .gitignore:

Сommit 90311bb706 contains the following change:

I can't go to the tspdf folder on the site.
Besides the master branch, there are no others.

@ELForcer Thanks! So when does the 500 happen exactly? When you click on the following?

I recorded a video where you can see that the repository works on the old version and does not work after the update:
https://yadi.sk/i/1W2H5uYHQMuL2w

Have the same issue here, but only on specific branches of the repo. I assume certain styles of commit histories break the system ?

I have same issue in a n home project:

An error has occurred : get submodule "tensorflow": revision does not exist

git push and clone works apparently.
Any update on that?

help me ,I have same issue
How to solve this problem

Workaround, use the old version (0.11). But her mail notification does not work, at least for me.

How did you solve this problem in the endHow did you solve this problem in the end

help me ,I have same issue
How to solve this problem

I just created a repository and pushed

git init
git add *
git commit -m 'init'
git push

I delete scriptsfolder, and redo push, it's fine.
Why can't handle submodules？

Use the old version (0.11). There is no such problem with submodule revisions, but notifications may not work.

On version 0.12.5 problem exists.

An error has occurred : get submodule "tcpdf": revision does not exist
Application Version: 0.12.5

However, the repository now opens without errors.
(I don’t know if this is the merit of Gogs or the owner of the current repository)
The problem only now remained in the old commit.

My colleague had this problem too.
Accoding to his description, he upload needless .git folder in second level folder.
Maybe the outer(the root directory) .git folder was breakdown also or his used wrong git command.

在根目录下添加.gitmodules
里面添加如下内容
[submodule "your_submodule_name"]
path = your_submodule_name
url = https://github.com/homealim2012/gcr.io_mirror.git
commit并push即可

My colleague had this problem too.
Accoding to his description, he upload needless .git folder in second level folder.
Maybe the outer(the root directory) .git folder was breakdown also or his used wrong git command.

I've successfully reproduced the behavior using this, looking into fix soon 🕵️ Though the error I got is a bit different:

get submodule "xxx": submodule does not exist

在根目录下添加.gitmodules 里面添加如下内容 [submodule "your_submodule_name"] path = your_submodule_name url = https://github.com/homealim2012/gcr.io_mirror.git commit并push即可

This is a solution which I tested and passed.

@unknwon since you added this issue to the 0.12.11 milestone, does that mean it is still not resolved in 0.12.10?

I'm having this issue on my local gogs install, but was unable to reproduce using try.gogs.io.

@unknwon since you added this issue to the 0.12.11 milestone, does that mean it is still not resolved in 0.12.10?

I'm having this issue on my local gogs install, but was unable to reproduce using try.gogs.io.

@esayre-um - Unfortunately no, that only means I'll attempt to fix it as part of 0.12.11 (which means the attempt could be a failure 😁 )

version 0.13.0 dev running in a docker container
is there a solution or workaround for this

I have run into and was able to reproduce exact same error

1. create new repository in gogs
2. create another new repo in gogs (or github, etc)
3. git clone repo#1
4. within repo#1, git clone repo#2
5. git add --all && git commit && git push
6. 500 error when visiting repo#1 in gogs web UI

adding .gitmodules with repo#2 details into repo#1 removes the 500 error in this case

gogs.log - 2023/02/11 16:18:05 [ERROR] [...gogs/internal/route/repo/view.go:57 renderDirectory()] get commits info: get submodule "wp": revision does not exist. -> gogs v0.12.9 git v2.34.1 go1.18.1 -> just related to submodules... best of luck on the fix. Thank you for your effort ✌🏼

I have run into and was able to reproduce exact same error

1. create new repository in gogs
2. create another new repo in gogs (or github, etc)
3. git clone repo#1
4. within repo#1, git clone repo#2
5. git add --all && git commit && git push
6. 500 error when visiting repo#1 in gogs web UI

adding .gitmodules with repo#2 details into repo#1 removes the 500 error in this case

Thank you @al-heisner! I successfully reproduced with these steps ❤️

On the surface looks like this happens when there is for whatever reason an undeclared submodule in the repository, will update Gogs to be more lenient about this.

The patch has landed in 0.13.0+dev, and will be back-ported to 0.12.11 (no ETA).

Great to hear… I too was having trouble reproducing this on this test server… curiously my repos seem to have the correct info in .gitmodules but still were giving me 500 errors.

The 0.12.11 has been released that includes the patch of the reported issue.

Thank you 👊🏼 updated to v0.12.11 and can confirm it fixes this issue.