Repo is frozen in time #1823

9001 commented 2025年03月16日 02:32:42 +01:00

Comment

One of my repos, 9001/copyparty appears to be frozen in time.

I am able to push and pull fresh commits over ssh, but nothing is happening in the web-UI, and I am also getting the same stale data as the UI if I clone over https.

This must have happened between 2024年06月01日 and 2024年07月16日 (july16 was my first push since june1st).

I've been waiting to report this since I figured it was a stuck cache or something, and it would be automatically corrected at some point, but it's been a while now. I'm also surprised that there doesn't appear to be anyone else encountering similar issues, so perhaps it's something I did somehow?

### Comment One of my repos, [9001/copyparty](https://codeberg.org/9001/copyparty) appears to be frozen in time. I am able to push and pull fresh commits over ssh, but nothing is happening in the web-UI, and I am also getting the same stale data as the UI if I clone over https. This must have happened between 2024年06月01日 and 2024年07月16日 (july16 was my first push since june1st). I've been waiting to report this since I figured it was a stuck cache or something, and it would be automatically corrected at some point, but it's been a while now. I'm also surprised that there doesn't appear to be anyone else encountering similar issues, so perhaps it's something I did somehow?

Gusted commented 2025年03月17日 13:18:10 +01:00

What is the git command you execute?

What is the git command you execute?

9001 commented 2025年03月17日 22:24:17 +01:00

I have a remote named all which has three push targets, so the command I run is git push all :

git remote -v
all	gh:9001/copyparty (push)
all	git@codeberg.org:9001/copyparty.git (push)
all	git@gitlab.com:9001/copyparty.git (push)

this correctly updates github and gitlab, and it correctly(?) pushes to gitlab, but the web-UI does not get updated with the new changes.

I also have a separate remote just for codeberg,

git remote -v
cb	git@codeberg.org:9001/copyparty.git (fetch)
cb	git@codeberg.org:9001/copyparty.git (push)

...but specifically pushing to codeberg with git push cb makes no difference.

for good measure, I have also tried all of the following:

git push
git push --all
git push --tags
git push all
git push all --all
git push all --tags

NOTE: if I run the following command, then I get a good checkout from codeberg which matches my local repo, with all the hundreds of commits made since july: git clone git@codeberg.org:9001/copyparty.git from-codeberg-ssh

but if I clone it over https instead of ssh, I get a repo which matches the web-UI, which is almost a year out of date: git clone https://codeberg.org/9001/copyparty.git from-codeberg-https

so I'm guessing something is stuck serverside?

I have a remote named `all` which has three push targets, so the command I run is `git push all` : ``` git remote -v all gh:9001/copyparty (push) all git@codeberg.org:9001/copyparty.git (push) all git@gitlab.com:9001/copyparty.git (push) ``` this correctly updates github and gitlab, and it correctly(?) pushes to gitlab, but the web-UI does not get updated with the new changes. I also have a separate remote just for codeberg, ``` git remote -v cb git@codeberg.org:9001/copyparty.git (fetch) cb git@codeberg.org:9001/copyparty.git (push) ``` ...but specifically pushing to codeberg with `git push cb` makes no difference. for good measure, I have also tried all of the following: ``` git push git push --all git push --tags git push all git push all --all git push all --tags ``` **NOTE:** if I run the following command, then I get a good checkout from codeberg which matches my local repo, with all the hundreds of commits made since july: `git clone git@codeberg.org:9001/copyparty.git from-codeberg-ssh` but if I clone it over https instead of ssh, I get a repo which matches the web-UI, which is almost a year out of date: `git clone https://codeberg.org/9001/copyparty.git from-codeberg-https` so I'm guessing something is stuck serverside?

Gusted commented 2025年03月19日 12:51:10 +01:00

@9001 wrote in #1823 (comment):

NOTE: if I run the following command, then I get a good checkout from codeberg which matches my local repo, with all the hundreds of commits made since july: git clone git@codeberg.org:9001/copyparty.git from-codeberg-ssh

This doesn't happen for me. Checking the git repository on the server, it reflects whats shown in the web UI. To be honest, it's really impossible that Codeberg is giving a different copy based on http or SSH, both uses the same git repository.

Could you please give the output when you execute the following command: git push cb -v --all

@9001 wrote in https://codeberg.org/Codeberg/Community/issues/1823#issuecomment-3084946: > **NOTE:** if I run the following command, then I get a good checkout from codeberg which matches my local repo, with all the hundreds of commits made since july: `git clone git@codeberg.org:9001/copyparty.git from-codeberg-ssh` This doesn't happen for me. Checking the git repository on the server, it reflects whats shown in the web UI. To be honest, it's really impossible that Codeberg is giving a different copy based on http or SSH, both uses the same git repository. Could you please give the output when you execute the following command: `git push cb -v --all`

9001 commented 2025年03月19日 19:06:50 +01:00

Man... turns out I fatfingered my ~/.ssh/config when I moved computers...

Case closed, sorry for the noise! And thanks for pointing me in the right direction :>

Man... turns out I fatfingered my ~/.ssh/config when I moved computers... Case closed, sorry for the noise! And thanks for pointing me in the right direction :>