Hi again, Reporting from an upgraded 3.1.1-1 container, the behavior is the same. Here is the log I see when I click on **Rebase** in case it helps:
weblate_1 | INFO enough/nextcloud: updating repository weblate_1 | INFO enough/nextcloud: update took 0.28 seconds weblate_1 | INFO enough/nextcloud: merge remote into repo weblate_1 | INFO enough/nextcloud: checking translationfiles/fr/enough.po (fr) [1/1] weblate_1 | INFO enough/nextcloud/fr: processing translationfiles/fr/enough.po, revision has changed weblate_1 | INFO enough/nextcloud: updating completed weblate_1 | 172.20.0.1 - - [27/Jul/2018:21:43:32 +0000] "POST /update/enough/?method=rebase HTTP/1.0" 302 0 "https://weblate.enough.community/"; "Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0" weblate_1 | [pid: 126|app: 0|req: 9/20] 172.20.0.1 () {52 vars in 1047 bytes} [Fri Jul 27 21:43:30 2018] POST /update/enough/?method=rebase => generated 0 bytes in 1579 msecs (HTTP/1.0 302) 10 headers in 639 bytes (1 switches on core 0) weblate_1 | INFO received GitLab notification on repository https://lab.enough.community/main/app, branch master, 0 matching components, 0 to process weblate_1 | 172.20.0.1 - - [27/Jul/2018:21:43:32 +0000] "POST /hooks/gitlab/ HTTP/1.0" 200 67 "-" "-" weblate_1 | [pid: 124|app: 0|req: 5/21] 172.20.0.1 () {42 vars in 561 bytes} [Fri Jul 27 21:43:32 2018] POST /hooks/gitlab/ => generated 67 bytes in 49 msecs (HTTP/1.0 200) 8 headers in 425 bytes (1 switches on core 0) weblate_1 | 172.20.0.1 - - [27/Jul/2018:21:43:33 +0000] "GET /projects/enough/ HTTP/1.0" 200 37263 "https://weblate.enough.community/"; "Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0" weblate_1 | [pid: 123|app: 0|req: 2/22] 172.20.0.1 () {48 vars in 1034 bytes} [Fri Jul 27 21:43:32 2018] GET /projects/enough/ => generated 37263 bytes in 766 msecs (HTTP/1.0 200) 12 headers in 762 bytes (1 switches on core 0) FWIW I see this error message which does not seem to be relevant because it is about Windows and I'm runing GNU/Linux July 27, 2018, 9:41 p.m. File format: rc Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/weblate/formats/models.py", line 50, in load_data fileformat.get_class() File "/usr/local/lib/python3.5/dist-packages/weblate/formats/ttkit.py", line 709, in get_class 'Windows RC file format is not supported on Python 3' ImportError: Windows RC file format is not supported on Python 3 Cheers On 07/27/2018 11:38 PM, Loïc Dachary wrote: > Hi Michal, > > Thanks for the quick reply, much appreciated on a Friday evening :-) > > I did the following: > > * - E - debian@weblate-host:/srv/weblate$ sudo docker-compose -f > docker-compose-infrastructure.yml logs -f weblate > * https://lab.enough.community/main/app/settings/integrations and clicked on > **test** > * saw the following output: > > weblate_1 | INFO received GitLab notification on repository > https://lab.enough.community/main/app, branch master,0 matching components, 0 > to process > weblate_1 | 172.20.0.1 - - [27/Jul/2018:21:22:14 +0000] "POST > /hooks/gitlab/ HTTP/1.0" 200 67 "-" "-" > weblate_1 | [pid: 124|app: 0|req: 1303/5723] 172.20.0.1 () {42 vars in > 561 bytes} [Fri Jul 27 21:22:14 2018] POST /hooks/gitlab/ => generated 67 > bytes in 31 msecs (HTTP/1.0 200) 7 headers in 398 bytes (1 switches on core 0) > > Which is encouraging: they seem to communicate well. Then I kept the logs -f > and pushed a change to the https://lab.enough.community/main/app repository > and saw: > > weblate_1 | INFO received GitLab notification on repository > https://lab.enough.community/main/app, branch master,0 matching components, 0 > to process > weblate_1 | 172.20.0.1 - - [27/Jul/2018:21:26:56 +0000] "POST > /hooks/gitlab/ HTTP/1.0" 200 67 "-" "-" > weblate_1 | [pid: 124|app: 0|req: 1305/5728] 172.20.0.1 () {42 vars in > 561 bytes} [Fri Jul 27 21:26:56 2018] POST /hooks/gitlab/ => generated 67 > bytes in 43 msecs (HTTP/1.0 200) 7 headers in 398 bytes (1 switches on core 0) > > which tells me the hook is taken into account. However, when I go to > https://weblate.enough.community/projects/enough/#repository, the latest > repository change is old. When I click **Rebase** on the **Repository tools** > panel to the right, it updates with the new value. > > I see weblate 3.1.1-1 was published a few hours ago and I'll give it a try > https://hub.docker.com/r/weblate/weblate/tags/ > > Thanks for the tip! > > On 07/27/2018 07:59 PM, Michal Čihař wrote: >> Hi >> >> On Fri, 2018-07-27 at 18:52 +0200, Loïc Dachary wrote: >>> In https://weblate.enough.community/ 3.0.1 weblate instance, the http >>> s://weblate.enough.community/projects/enough project is setup with ht >>> tps://lab.enough.community/main/app/ and initialized correctly. The h >>> ttps://weblate.enough.community/hooks/gitlab/ hook was added in >>> GitLab and tested to work at https://lab.enough.community/main/app/se >>> ttings/integrations. However it does not trigger anything and https:/ >>> /weblate.enough.community/projects/enough/#repository stays >>> unmodified. If I click pull on this page, the update happens as >>> expected. >>> >>> Obviously I'm missing something, probably trivial, and I would very >>> much appreciate any idea you may have to guide me in the right >>> direction. >> >> Check the application logs (by default they are sent to syslog), maybe >> repository URL does not match. Anyway Weblate 3.1 contains some >> improvements in this (originally targeted at BitBucket, but might help >> in your case as well). >> >> >> >> _______________________________________________ >> Weblate mailing list >> [email protected] >> https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate >> > -- Loïc Dachary, Artisan Logiciel Libre
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Weblate mailing list [email protected] https://lists.cihar.com/cgi-bin/mailman/listinfo/weblate
