No files shown in repository after uploading an existing repository

[hamishmb]

Gogs version

0.12.3

Git version

• Server: 2.25.1
• Client: 2.25.1

(Both are running the same OS: Linux Mint 20.3)

Operating system

Linux Mint 20.3

Database

SQLite 3

Describe the bug

Seems to be the same as this bug: #3697

Step 1: create git repository with gogs web interface
Step 2: add git repository as remote to local repository with SSH
Step 3: push changes to remote origin

Result: After upload is finished (~100MB) no Browse is shown, only the description of how to clone the repository.

To reproduce

I don't know how to reproduce this - on the second try after deleting and recreating the repo with the same name, it worked fine.

Expected behavior

Expectation: After finished upload, the Browse option should be possible and the files visible within the web interface

Additional context

I know this is an older version of GOGS, but I couldn't find any other issues about this, so to the best of my knowledge this doesn't seem to have been fixed.

I'm unsure if there's anything sensitive in the gogs.log file. The repositories on this machine are private, so I am reluctant to upload without more information about what's in the log.

Code of Conduct

• I agree to follow this project's Code of Conduct

[unknwon]

Hey!

Step 1: create git repository with gogs web interface

Just to confirm, did you create an empty repository?

Step 2: add git repository as remote to local repository with SSH

What is the remote URL looks like? And did you use the one copied from the web UI?

It is common with incorrect SSH URL would make push did not call Gogs's callback which updates the repository state.

[hamishmb]

Hi there.

Yes, I created an empty repository (didn't initialise with README or LICENSE files during creation).

The URL in the web UI is a http://localhost:3000/hamishmb/ format, but as I pushed from a different machine I had to use http://192.168.10.212:3000/hamishmb/. I can provide the exact names if you want.

I used the history feature of my terminal to run exactly the same commands the second time, so I know that there were no differences between runs (I checked that no other repos had appeared after it behaved oddly the first time I tried pushing the files).

Cheers,
Hamish

[unknwon]

Step 2: add git repository as remote to local repository with SSH

"http://192.168.10.212:3000/hamishmb/" is an HTTP URL not SSH, I'm a bit confused on what the "step 2" means now 🤔

---

Workaround is just to create the repository with something then pull to start.

[hamishmb]

My bad, I use http for this server, not ssh.

[unknwon]

No worries!

Could you try running the following action in the /admin

Then do a new push?

[hamishmb]

Would that be useful, now the repo is working? It only did this once, and it then worked on the second try after deleting and recreating the repo.

[unknwon]

It only did this once, and it then worked on the second try after deleting and recreating the repo.

Could you speak with more context? what is "this", "it", and second try of "what"?

[hamishmb]

Okay, fair enough.

I only saw the bug in the bug description a single time - it didn't happen after deleting the repo and trying to push the same files to it again. Knowing this, would it still be useful for me to try that action?

I'm happy to create new repos and push the same files over and over try to try reproduce the problem, and then try the action, if that might help?

[unknwon]

I only saw the bug in the bug description a single time - it didn't happen after deleting the repo and trying to push the same files to it again. Knowing this, would it still be useful for me to try that action?

Hmm, I don't understand this... how could you continue to push files after deleting the repo you're trying to push to?

[hamishmb]

I deleted it and then recreated it.

[unknwon]

I deleted it and then recreated it.

Ah gotcha! Yeah, in that case, it sounds like it was just something went wrong unexpected for a single time. The recreation of the repository is effectively the "re-sync hooks" action for that single repository, no need to do that anymore.