From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [RFE] Migration to gitlab Date: Sat, 11 May 2019 15:13:21 +0300 Message-ID: <8336lldw9q.fsf@gnu.org> References: <1552789070.5272.1@yandex.ru> <87imwhmmt8.fsf@gmail.com> <87y347g1l3.fsf@iotcl.com> <9ac21e82-8e47-f9b5-f88d-23c0c56946d1@yandex.ru> <87pnpc1lby.fsf@iotcl.com> <83zhoezdqc.fsf@gnu.org> <87imuivfcr.fsf@iotcl.com> <83k1eyfxls.fsf@gnu.org> <3b8e2195-07c0-a240-6164-8d34bcca344f@yandex.ru> <83ftpmfp0y.fsf@gnu.org> <838svefl3p.fsf@gnu.org> <0C7B0831-187D-413C-B4F6-5AB542A7AA1A@icloud.com> <22f3aceb-e562-b1ee-03da-90d29b007b46@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="266327"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, pcr910303@icloud.com, dgutov@yandex.ru, toon@iotcl.com, agrambot@gmail.com To: =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 11 14:13:37 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hPQsi-00177D-E0 for ged-emacs-devel@m.gmane.org; Sat, 11 May 2019 14:13:36 +0200 Original-Received: from localhost ([127.0.0.1]:58201 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPQsh-0005Vv-4W for ged-emacs-devel@m.gmane.org; Sat, 11 May 2019 08:13:35 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:45985) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPQsb-0005Vd-3R for emacs-devel@gnu.org; Sat, 11 May 2019 08:13:30 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:38423) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hPQsX-0002jD-Gy; Sat, 11 May 2019 08:13:25 -0400 Original-Received: from [176.228.60.248] (port=3065 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hPQsW-0003YN-PP; Sat, 11 May 2019 08:13:25 -0400 In-reply-to: <22f3aceb-e562-b1ee-03da-90d29b007b46@gmail.com> (message from =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel on Fri, 10 May 2019 11:26:55 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:236413 Archived-At: > Cc: toon@iotcl.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca, > agrambot@gmail.com, Dmitry Gutov > From: Clément Pit-Claudel > 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 concern.