-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Hook doesnt run on push #22466
Comments
Did you try running the Synchronize hooks admin task after updating the What did you update the LOCAL_ROOT_URL to? |
Yes, and I just retry with my testing VM and same result, hooks doesn't execute on push.
I'm not sure to understand, I'm not a very good english speeker, but I have update LOCAL_ROOT_URL in section [server] of my app.ini config file, as you can see in the gist I linked previously. |
As per #22370 (comment) Try running gitea with the environment variable This is all related to #22370 and should be fixed by #22467 #22468 I am going to mark this as a duplicate of that. |
I just tried, on gitea 1.18.0 without LOCAL_ROOT_URL set, and same result as my starting point with 1.18.0, push are refused with this error on client side :
With LOCAL_ROOT_URL set, push are accepted but hooks are not executed. I don't know if gitea takes the environment variable into account, I don't see anything about it in the logs when the process starts. The variable is well defined, I can display it from the command prompt
|
I don't know what you've done but your hooks haven't been updated when you updated the LOCAL_ROOT_URL:
I thought you said you'd set your In terms of the workaround GODEBUG environment variable, if thas has been set it should also propagate to any calls of hooks within http. So I'm not sure that you've set that correctly either. However, there is a fix already available. Download and run the current 1.18-dev from: |
Sorry, maybe I should have said this earlier but yes when I use the LOCAL_ROOT_URL parameter, it has the value In my report of the previous post, I defined the environment variable GODEBUG and then I tested to push a first time without the parameter LOCAL_ROOT_URL defined in the config (the logs provided are from that case), then I tested to push a second time with this time the parameter LOCAL_ROOT_URL defined. Your version 1.18-dev solve all my issues, push are accepted and hooks executed, thanks for your time. |
Description
After updating gitea to 1.18, the pushes were not accepted anymore, I followed the recommendations of this ticket which corresponded to my issue: #22381
Once the LOCAL_ROOT_URL parameter was set, the pushes were accepted again but on the other hand the hooks of the repositories managed by Gitea were not executed anymore and the pushs dosnt showed up anymore on dashboard activiy. I found this ticket #22319 corresponding to the symptoms we noticed, but contrary to the author of the ticket, on my server, Gitea is the only process to use port 3000.
I did a rollback to 1.17.4, then to 1.17.3 (last version used before the upgrade), but the problem of the unexecuted hook was still present.
The LOCAL_ROOT_URL parameter was still present in the conf, once removed, the hook execution was restored.
I was able to reproduce the bug on a VM windows server 2016 standard 64 bits and isolate the combination of factor that in my case prevents the execution of hooks : https + LOCAL_ROOT_URL config item setup, without https the hooks are executed.
The logs I send you are from version 1.17.3 of gitea, version 1.17.4 and 1.18.0 produce the same logs, if needed I can provide them too.
Gitea Version
1.18.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
https://gist.github.com/Bartabat/b7aa778754646bf2bc7c5212c1fdd396
Screenshots
Not relevant.
Git Version
2.39.0.windows.2
Operating System
Windows server 2016 essential - 64 bits
How are you running Gitea?
Running as windows service.
Download binary with go-git embedded : https://dl.gitea.io/gitea/1.18.0/gitea-1.18.0-gogit-windows-4.0-amd64.exe
Database
MySQL
The text was updated successfully, but these errors were encountered: