Closed Davidbrcz closed 8 months ago
I am getting the same error, also using a self hosted GitLab.
A quick fix is to add &optional callback
to the forge--pull
definition in forge-gitlab.el
, i.e.:
(cl-defmethod forge--pull ((repo forge-gitlab-repository) until
&optional callback)
It isn't actually calling the callback
, which was added in https://github.com/magit/forge/commit/02cd2836c6cf603ce50c6c204471bfb77fc45f1e , apparently to speed up refreshing in some cases, so I don't know if this breaks anything else.
The optional callback
argument was added to the GitHub integration in https://github.com/magit/forge/commit/896a934f622ee8bcaf88dabcc08d085cdccc6482 , way back in 2019, but it didn't make it to the Gitlab integration.
It's unblocked me (so far) but YMMV.
@jamadden Thanks for digging up the relevant commits.
Thanks @tarsius and @jamadden, it is working again. :)
Hello
I work with a self hosted gitlab forge (everything has been working great for the last 3 years). This week,
forge-pull
yields an error, and nothing gets pulledThe full backstrace
Tried to recompiled .emacs.d and to remove it altogether to get a fresh install of packages. error still there.
Magit version 20240125.1835 Forge version 20240127.1100
Thanks !
PS: Love magit & forge, awesome work.