[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFE] Migration to gitlab

From: Eli Zaretskii
Subject: Re: [RFE] Migration to gitlab
Date: Sat, 11 May 2019 15:13:21 +0300

> Cc: address@hidden, address@hidden, address@hidden,
>  address@hidden, Dmitry Gutov <address@hidden>
> From: Clément Pit-Claudel <address@hidden>
> Date: Fri, 10 May 2019 11:26:55 -0400
> I set out to write detailed instructions, but gave up halfway, because forge 
> didn't work for that use case.  Indeed, the way forge deals with issues and 
> merge requests is to download the full issue database of the project.  For 
> Gitlab, with 27000 merge requests and 50000 issues, the software spent 
> multiple of minutes attempting to download this humongous database, and then 
> gave up and threw an exception.  Accordingly, I gave up and didn't post my 
> instructions (Eli, they are below, if you are curious to try them on a 
> smaller repository; forge is indeed great when it can handle the repo size).
> I do not know whether Emacs' issue database is large enough to cause issues. 
> Additionally, I understand that thigs may improve in the future, because 
> forge currently uses an inefficient communication protocol to talk to Gitlab 
> (but there are plans to support a better protocol in Gitlab, I think).  I do 
> not know whether things will work better once Gitlab implements a better 
> protocol (I hope they will!).  In the meantime, we should be careful about 
> assuming that forge will solve the problem of browsing Gitlab issues from 
> Emacs.
> Below are the instructions I had started to write.

Thank you very much for your efforts.

Is there any way of knowing at what number of issues for forge choke
when downloading the database?  We have a good idea of how many issues
we have in ours, so we could figure out if this problem will be of any

reply via email to

[Prev in Thread] Current Thread [Next in Thread]