TL;DR. Given somewhat slower-than-expected progress on the Trac import I
suggest that we implement a pared-down migration on Tuesday.
See "The Plan" below.
Hello everyone,
Over the last few weeks we have been hard at work preparing the
migration to GitLab. Currently the following t
Hi,
Am Montag, den 17.12.2018, 00:29 -0500 schrieb Ben Gamari:
> 2. We begin officially accepting merge requests on this fresh GitLab
> instance on Tuesday. At this point gitlab.haskell.org:ghc/ghc will
> become GHC's official upstream repository.
I guess this works only because GitLab h
Hi Ben - this sounds good, a couple of questions:
- What about the performance issue we noticed last week?
- What will happen to Phabricator diffs that are still mid-review? It would
be a shame to have to move them to gitlab and interrupt the review trail.
Can't we just shut Phabricator to new dif
Hi Ben,
in my experience Gitlab has been extremely slow at showing commit diffs to
the point that it gives up and returns a 502:
https://gitlab.staging.haskell.org/ghc/ghc/issues/15944
Is this possibly related to any resource constraints on our instance?
Cheers,
Simon
Am Mo., 17. Dez. 2018 um 0
Simon Jakobi via ghc-devs writes:
> Hi Ben,
>
> in my experience Gitlab has been extremely slow at showing commit diffs to
> the point that it gives up and returns a 502:
> https://gitlab.staging.haskell.org/ghc/ghc/issues/15944
>
> Is this possibly related to any resource constraints on our inst
Simon Marlow writes:
> Hi Ben - this sounds good, a couple of questions:
>
> - What about the performance issue we noticed last week?
I identified the problem as being the ARM environment which the staging
instance is running on. The final instance will run on x86_64.
> - What will happen to Ph
> On Dec 17, 2018, at 10:52 AM, Ben Gamari wrote:
>
>>
>> - What will happen to Phabricator diffs that are still mid-review? It would
>> be a shame to have to move them to gitlab and interrupt the review trail.
>> Can't we just shut Phabricator to new diffs but keep the possibility of
>> worki
Hey simon!
I actually did some digging. And it looks like currently gitlab basically
does a git diff of the two branches and does that computation on every page
reload.
1). There currently is no caching —- some of the folks on the Haskell infra
team could help perhaps but they need to be given acc
