[BUG] In 1.15.0, git push activites does not work, webhook on push not work

[duchenpaul]

• Gitea version (or commit ref): 1.15.0+dev-578-g8464fa15d
• Git version:
• Operating system: official docker
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (You edit a file commit it, this behavior will not show up in the dashboard, and if you have webhook, it will not trigger)
  • No
• Log gist:
  Sorry, but I dont see any error/abnormals in logs of gitea.

Description

I upgraded my gitea image to the latest version in dockerhub.
And the webhook no longer works, I found that my git push activities are not presenting in my dashboard.
Looks like the new version gitea totally missed my git push activities.

Action
You push a commit to a repo.

Expected

• Your commit shows up in the dashboard, like below,
  

• The webhook of this repo will be triggered by this push

Actual

• You can see your commit in the source code page
• But your commit does not show up in the dashboard
• The webhook is not triggered

Below is my recordings about that, all I test is to push a commit into the repo, and expect this action to be shown in the dashboad, and demostrate that it works in the older version, and not working in the newest one

Screenshots

Git activities works in v1.14.4

Git activities breaks in v1.15.0

[zeripath]

I'm likely being completely dense but I can't for the life of me understand what it is that is not happening when it should and what it is that you're trying to do.

The videos are not that helpful by themselves. Please describe what it is you are doing.

[duchenpaul]

I'm likely being completely dense but I can't for the life of me understand what it is that is not happening when it should and what it is that you're trying to do.

The videos are not that helpful by themselves. Please describe what it is you are doing.

Sorry for the inconvinience, I expanded more details about the issue, if you have any questions, please let me know

[lunny]

I cannot reproduce this on my local macOS Gitea instance.

[zeripath]

I suspect that you need to resynchronize the hooks.

Also ensure that your repositories are not being mounted as noexec

[zeripath]

Your browser is obscuring the most important part of the logs too. When you make the push there should be a call to:

api/internal/hook/pre-receive/:owner/:repo and api/internal/hook/post-receive/:owner/:repo

if that's not there then it's clear that your hooks aren't either being run or are being sent to the wrong place.

[duchenpaul]

Take a step back, on https://try.gitea.io,
when you push a change, there should be an update to the dashboard, saying :username pushed to :branch_name at :repo_name, like so:

I just tried to do so in https://try.gitea.io, there is no such update on my dashboard.
The url is here: https://try.gitea.io/duchenpaul/Hosted

You can see the last commit is Thu, 15 Jul 2021 00:17:11 UTC

if you go to my profile, the last update is Wed, 14 Jul 2021 15:52:44 UTC, which the time when the repo was forks, not get updated by my push.

[duchenpaul]

In order to reproduce, please:

• create/fork a repo in https://try.gitea.io/
• Push a commit
• if you have a webhook, check its Recent Deliveries to see if it is triggered

[multicast]

I can confirm; I have the same behavior in 1.15.0+dev-582-g3dcb3e907

Creating a new repository via UI, copy/paste initial commands and pushing README to master, and UI never shows code, but the introductory message. I veriefied that the data are actually pushed and the bare repository has the "first commit" pushed, but web-UI still displays hint on how to add origin or make first commit.

[duchenpaul]

@multicast yeah, if you use webhook, it won't trigger

[multicast]

@duchenpaul no, create repo, git init/touch/add...push, and the repo on the web looks like no push happened. but repositories/user/name.git does contain the commit. there is no special webhook added yet to newly created repo yet.

[Xenolphthalein]

I can reproduce this issue with a newly created docker instance on 1.15.0 (latest).

• Create a docker container with 1.15.0 (latest)
• Go through the basic configuration
• Configure your ssh key
• Create a new repository
• Push to that repository via ssh
• Find that the repository still shows the Setup Guide in the Web GUI
• Cloning the repository from the remote to another folder works as expected

If you revert to 1.14.4 everything works as expected.

[multicast]

I was now on the same journey and confirm :latest tag is buggy and :1.14.4 works.

The database version has been bumped since 1.14.4 several times, what issues I can expect when looking at models/migrations/v178 ... 188.go?

[zeripath]

I can reproduce this issue with a newly created docker instance on 1.15.0 (latest).

• Create a docker container with 1.15.0 (latest)
• Go through the basic configuration
• Configure your ssh key
• Create a new repository
• Push to that repository via ssh
• Find that the repository still shows the Setup Guide in the Web GUI
• Cloning the repository from the remote to another folder works as expected

If you revert to 1.14.4 everything works as expected.

I just did this and could not reproduce.