Re: Gitlab access

Approved. On Thu, Sep 26, 2024 at 11:37 AM Vandenbroucke, Alexander via ghc-devs < ghc-devs@haskell.org> wrote: > PUBLIC > > Hi ghc-devs, > > > > Can someone please approve my request for a gitlab account ( > alexander.vandenbrou...@sc.com). > > > > I would like to report a bug. > > > > Kind Rega

Re: GitLab Approval

Hello Jose, I’ve approved your account. Welcome! Feel free to reach out if you have any questions. Cheers, Rodrigo Mesquita > On 6 Aug 2024, at 13:56, Jose Lane wrote: > > I am looking to get my gitlab account approved. user name: Forist2034 > ___ >

Re: Gitlab upgrade tomorrow

The upgrade to 17.1.2 is now completed. Cheers, Matt On Tue, Jul 16, 2024 at 10:08 AM Matthew Pickering wrote: > > The upgrade to 1.17.1 is completed now, migrations are running in the > background. Please post if there are any issues, it's the first > upgrade I have done. > > I will perform th

Re: Gitlab upgrade tomorrow

The upgrade to 1.17.1 is completed now, migrations are running in the background. Please post if there are any issues, it's the first upgrade I have done. I will perform the upgrade to 1.17.2 once the corresponding patch lands in upstream. (https://github.com/NixOS/nixpkgs/pull/326259/files) Chee

Re: GitLab upgrade later today

Ben Gamari writes: > Hi all, > > I will be performing a GitLab upgrade later this evening (likely around > 18:00 EDT). I expect this will take only a few minutes. > The upgrade is complete. As always, let me know if anything looks amiss. Cheers, - Ben signature.asc Description: PGP signature

Re: GitLab approval

mari >> To: ghc-devs@haskell.org >> Cc: >> Bcc: >> Date: Wed, 09 Aug 2023 03:07:37 -0400 >> Subject: Re: GitLab approval >> I am a bit confused. It appears that you account has been active since >> 2018. >> >> >> On August 8, 2023 11:55:01

Re: GitLab approval

Forwarded message -- > From: Ben Gamari > To: ghc-devs@haskell.org > Cc: > Bcc: > Date: Wed, 09 Aug 2023 03:07:37 -0400 > Subject: Re: GitLab approval > I am a bit confused. It appears that you account has been active since > 2018. > > > On August 8, 2023 11

Re: GitLab approval

I am a bit confused. It appears that you account has been active since 2018. On August 8, 2023 11:55:01 PM EDT, cydparser wrote: >Can a GitLab admin please approve my account (@cydparser). Thanks! ___ ghc-devs mailing list ghc-devs@haskell.org http://ma

Re: GitLab partial outage - attempting to mitigate

Brandon Allbery writes: > Isn't it just "move /nix out of the way, bind mount a new one from a > larger drive, use rsync to move the data"? > Something like that, yes [1]. Cheers, - Ben [1] https://nixos.wiki/wiki/Storage_optimization#Moving_the_store signature.asc Description: PGP signatur

Re: GitLab partial outage - attempting to mitigate

Ben Gamari writes: > Bryan Richter via ghc-devs writes: > >> I eventually resorted to a server reboot, which cleared up all the problems >> I was seeing. I think we're back in business. >> > The root partition was close to running out of disk space yesterday. The > problem appears to be that /ni

Re: GitLab partial outage - attempting to mitigate

Isn't it just "move /nix out of the way, bind mount a new one from a larger drive, use rsync to move the data"? On Mon, Mar 20, 2023 at 9:25 AM Ben Gamari wrote: > > Bryan Richter via ghc-devs writes: > > > I eventually resorted to a server reboot, which cleared up all the problems > > I was see

Re: GitLab partial outage - attempting to mitigate

Bryan Richter via ghc-devs writes: > I eventually resorted to a server reboot, which cleared up all the problems > I was seeing. I think we're back in business. > The root partition was close to running out of disk space yesterday. The problem appears to be that /nix is located on the small syste

Re: GitLab partial outage - attempting to mitigate

I eventually resorted to a server reboot, which cleared up all the problems I was seeing. I think we're back in business. Symptoms were: * No new data coming into https://grafana.gitlab.haskell.org/d/iiCppweMz/marge-bot?orgId=2&from=now-7d&to=now&refresh=30m * High-frequency repetition of the sys

Re: GitLab maintenance has started

Looks like artifacts are being successfully uploaded now! I think I'm actually done now. Happy Haskelling, -Bryan On Thu, Nov 24, 2022 at 1:43 PM Bryan Richter wrote: > > Jobs are getting picked up, but now it looks like they are failing to > upload artifacts. I am looking into it now. > > On

Re: GitLab maintenance has started

Jobs are getting picked up, but now it looks like they are failing to upload artifacts. I am looking into it now. On Thu, Nov 24, 2022 at 11:51 AM Bryan Richter wrote: > > I can confirm that! Great! > > [Attached screenshot shows runners online in the GitLab Runners Admin UI] > > On Thu, Nov 24,

Re: GitLab maintenance has started

I can confirm that! Great! [Attached screenshot shows runners online in the GitLab Runners Admin UI] On Thu, Nov 24, 2022 at 11:49 AM Moritz Angermann wrote: > > The zw3rk runners should be back. > > On Thu, 24 Nov 2022 at 17:41, Bryan Richter via ghc-devs > wrote: >> >> Hello again, >> >> Aft

Re: GitLab maintenance has started

The zw3rk runners should be back. On Thu, 24 Nov 2022 at 17:41, Bryan Richter via ghc-devs < ghc-devs@haskell.org> wrote: > Hello again, > > After a few surprises, I have finished my migration. > > Unfortunately, CI IS STILL BROKEN. > > All CI runners disabled themselves while GitLab was in maint

Re: GitLab maintenance has started

Hello again, After a few surprises, I have finished my migration. Unfortunately, CI IS STILL BROKEN. All CI runners disabled themselves while GitLab was in maintenance mode. (That's not very helpful, but never mind.) As I do not have the access or privileges required to restart the runners, the

Re: GitLab runners having issues

Update: spurious failure tracking has been fixed! On Wed, Nov 9, 2022 at 10:22 AM Bryan Richter wrote: > > It looks like this was "resolved" -- it was an intermittent issue that > went away on its own. I will start tracking it appropriately. > > Speaking of which, tracking spurious failures is no

Re: Gitlab slow?

It is fast again now... Simon On Mon, 14 Nov 2022 at 16:35, Ben Gamari wrote: > Bryan Richter via ghc-devs writes: > > > I find it very slow, as well. :( > > > > Eventually I want to be able to help out with these problems, but > > right now my priorities are different and I don't have the ban

Re: Gitlab slow?

I believe we can get a long way with enabling tracing in our GitLab instance, especially since Grafana can be used for visualisation, through its associated product Tempo (which is compatible with Jaeger). https://docs.gitlab.com/ee/development/distributed_tracing.html Le 14/11/2022 à 17:33, B

Re: Gitlab slow?

Bryan Richter via ghc-devs writes: > I find it very slow, as well. :( > > Eventually I want to be able to help out with these problems, but > right now my priorities are different and I don't have the bandwidth. > We rely on Ben still. (I am at least relieving him of other tasks that > would be c

Re: Gitlab slow?

I find it very slow, as well. :( Eventually I want to be able to help out with these problems, but right now my priorities are different and I don't have the bandwidth. We rely on Ben still. (I am at least relieving him of other tasks that would be competing for his time!) On Mon, Nov 14, 2022 at

Re: GitLab runners having issues

Thanks for the update Bryan! Le 09/11/2022 à 09:22, Bryan Richter via ghc-devs a écrit : It looks like this was "resolved" -- it was an intermittent issue that went away on its own. I will start tracking it appropriately. Speaking of which, tracking spurious failures is not functioning right no

Re: GitLab runners having issues

It looks like this was "resolved" -- it was an intermittent issue that went away on its own. I will start tracking it appropriately. Speaking of which, tracking spurious failures is not functioning right now, due to a problem with the ghc-perf-import bot. Until that gets resolved (later today, no

Re: GItlab search

Simon Peyton Jones writes: > Friends > > I'm struggling with GitLab search. > > eg I was looking for #22200 > > I wen to https://gitlab.haskell.org/ghc/ghc/-/issues, and put "-DEEBUG" and > "slow" in the search box. No #22200. Yet both of those strings appear in > the title of the ticket. > Oh

Re: Gitlab labels

I agree this is annoying. I have found "quick actions" [1] useful in alleviating the frustruation somewhat. One can issue short commands, into the comment box. e.g /relabel ~HPC ~documentation ~"T::task" ~"P::high" there's a completion interface so it's very straightforward. [1] https://gitlab.

Re: Gitlab labels

I haven't looked into it yet. As I haven't seen this problem on any other instance of GitLab, I have a hunch it's unique to gitlab.haskell.org. I'd like to look into it eventually. -Bryan On 28/07/2022 12:55, Zubin Duggal wrote: The error is bogus, if you refresh the page you will see that

Re: Gitlab labels

The error is bogus, if you refresh the page you will see that the label has been updated. This seems to be a bug in Gitlab, and I've also been seeing it a lot more often recently. I think Bryan attempted to investigate at a certain point, but I don't know what came of it. On 22/07/28 10:51, Simo

Re: GitLab bullets

Thank you. Looks nice again! S On Fri, 10 Jun 2022 at 16:01, Ben Gamari wrote: > Simon Peyton Jones writes: > > > Ben > > > > GitLab's rendering has become broken. See this ticket > > https://gitlab.haskell.org/ghc/ghc/-/issues/20686 > > > >- look under "Common ground...". The bullets

Re: GitLab bullets

Simon Peyton Jones writes: > Ben > > GitLab's rendering has become broken. See this ticket > https://gitlab.haskell.org/ghc/ghc/-/issues/20686 > >- look under "Common ground...". The bullets all have a newline after >them >- Ditto the numbered points under "Generalisation" >- B

Re: GitLab bullets

It might be fixed by [1], that is part [2] of the latest release v15.0.2. Giorgio [1] https://gitlab.com/gitlab-org/gitlab/-/merge_requests/87904 [2] https://about.gitlab.com/releases/2022/06/06/gitlab-15-0-2-released/ On Thu, 9 Jun 2022 at 16:37, Simon Peyton Jones wrote: > > Ben > > GitLab's

Re: GitLab upgrade starting shortly

Hello all, GitLab is back up and is fully upgraded. You may now continue with your usual business. Cheers, - Ben signature.asc Description: PGP signature ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo

Re: GitLab upgrade starting shortly

Hello all, As noted yesterday, there is one final (hopefully short!) outage needed to complete the upgrade process. This will begin in around 20 minutes, at 20:00 EST. I'll notify the list when it has finished. Cheers, - Ben signature.asc Description: PGP signature ___

Re: GitLab upgrade starting shortly

GitLab is again up and churning through the next round of migrations which is yet again taking quite a bit longer than expected. I will need to arrange another r short outage tomorrow to finish the final phase of the upgrade but it will remain up and usable until then. Cheers, - Ben On June

Re: GitLab upgrade starting shortly

Ben Gamari writes: > Ben Gamari writes: > >> Hello all, >> >> I will be starting the GitLab upgrade shortly. Expect approximately 30 >> minutes of downtime. >> > The service is back up temporarily but currently performing background > migrations, which are taking longer than expected. There will

Re: GitLab upgrade starting shortly

Ben Gamari writes: > Hello all, > > I will be starting the GitLab upgrade shortly. Expect approximately 30 > minutes of downtime. > The service is back up temporarily but currently performing background migrations, which are taking longer than expected. There will be two more periods of brief dow

Re: gitlab spam

Moritz Angermann writes: > The second one is an issue if it consumes CI Ressource. Ideally we’d have > only “blessed” repos allowed to consume CI. The issue with this is that > (random) new users can’t fork GHC and have CI run against their change. > > I’d still very much like to see a solution t

Re: gitlab spam

The second one is an issue if it consumes CI Ressource. Ideally we’d have only “blessed” repos allowed to consume CI. The issue with this is that (random) new users can’t fork GHC and have CI run against their change. I’d still very much like to see a solution to this; it is a security concern. M

Re: gitlab spam

Bryan and I discussed this in person but I'll repeat what I said there here: In short, there are two kinds of spam: * user creation without the creation of any other content * spam content (primarily projects and snippets) My sense is that the former has thusfar been harmless and consequently

Re: gitlab spam

No visible effect on my part, but I would agree that it's not something we should keep. :) Le 16/05/2022 à 15:52, Bryan a écrit : While familiarizing myself with gitlab.haskell.org, I noticed there's a ton of spam users and projects. Does this have any practical effect on any of you? Who (if

Re: Gitlab problem

Thanks. It has mysteriously started working again now... Sorry for the noise. Simon On Tue, 10 May 2022 at 17:01, Matthew Pickering wrote: > Hi Simon, > > I can't reproduce this locally.. still broken for you? > > Matt > > On Tue, May 10, 2022 at 4:32 PM Simon Peyton Jones > wrote: > > > >

Re: Gitlab problem

Hi Simon, I can't reproduce this locally.. still broken for you? Matt On Tue, May 10, 2022 at 4:32 PM Simon Peyton Jones wrote: > > Friends > > I am abruptly unable to push or pull to the GHC repo. E.g. 'git fetch' just > hangs. > > Yet ssh g...@gitlab.haskell.org seems to succeed with > PTY

Re: GitLab likes Chrome more than Firefox

> On a tip from Ben, I'm using Chrome to review a large patch (!7033 for the > curious). It is qualitatively better than Firefox, my usual tool. And to follow up from this morning, I fear that Magit is not going to be useful as a tool for reviewing: it seems unable to access the "conversation"

RE: Gitlab

Simon Peyton Jones via ghc-devs writes: > It started working again, a few mins after it stopped working. I was > getting consistent Error 500, then started being OK. > > Strange. > Indeed there was a misconfiguration that caused this sort of intermittent failure which I have now fixed. Apoloegie

RE: Gitlab

. (For now, it just forwards to simo...@microsoft.com.) | -Original Message- | From: ghc-devs On Behalf Of Tom Ellis | Sent: 21 October 2021 10:07 | To: ghc-devs@haskell.org | Subject: Re: Gitlab | | On Thu, Oct 21, 2021 at 08:59:48AM +, Simon Peyton Jones via ghc- | devs

Re: Gitlab

Yes, when visiting gitlab.haskell.org, but it seems to be OK again now. Sam ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab

On Thu, Oct 21, 2021 at 11:10:38AM +0200, Sam Derbyshire wrote: > I'm also getting error 500 now. Where? When visiting gitlab.haskell.org in your browser or when using git on the command line? Tom ___ ghc-devs mailing list ghc-devs@haskell.org http://m

Re: Gitlab

I'm also getting error 500 now. Sam ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab

On Thu, Oct 21, 2021 at 08:59:48AM +, Simon Peyton Jones via ghc-devs wrote: > Is it just me, or is Gitlab offline again? I'm getting error code 500. I just checked the following, which all work fine: * Navigate to https://gitlab.haskell.org/ghc/haddock (in Firefox) * git clone https://gitl

Re: Gitlab

Working for me. Matt On Thu, Oct 21, 2021 at 10:01 AM Simon Peyton Jones via ghc-devs wrote: > > Is it just me, or is Gitlab offline again? I’m getting error code 500. > > Simon > > > > PS: I am leaving Microsoft at the end of November 2021, at which point > simo...@microsoft.com will cease to

Re: Gitlab

It's working for me at the moment. Sam ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab outage

Norman Ramsey writes: > > Unfortunately yesterday gitlab.haskell.org yet again ran out of disk > > space. It is currently being migrated to another machine and in the > > meantime things may be a bit flaky. Many apologies for the > > inconvenience. More updates will be coming as the situation

Re: GitLab outage

Ben Gamari writes: > Hello all, > > Unfortunately yesterday gitlab.haskell.org yet again ran out of disk > space. It is currently being migrated to another machine and in the > meantime things may be a bit flaky. Many apologies for the > inconvenience. More updates will be coming as the situation

Re: GitLab outage

> Unfortunately yesterday gitlab.haskell.org yet again ran out of disk > space. It is currently being migrated to another machine and in the > meantime things may be a bit flaky. Many apologies for the > inconvenience. More updates will be coming as the situation develops. I see that gitlab is

Re: GitLab summary note on review

Richard Eisenberg writes: > Hi devs, > > I've frequently wanted to attach a summary note to a review, > unattached to any line of code. I thought this was impossible, but I > see how to do it now. > > After making your review, with perhaps many line comments, go back to > the Overview pane. Then,

Re: GitLab downtime

It looks like this is the result of the recurrence of a nixpkgs issue. I have applied a potential workaround. Cheers, - Ben On June 2, 2021 12:26:26 AM EDT, Giorgio Marinelli wrote: >502 again. > > >Giorgio > > >On Tue, 1 Jun 2021 at 10:20, Matthew Pickering > wrote: >> >> I restarted the ser

Re: GitLab downtime

502 again. Giorgio On Tue, 1 Jun 2021 at 10:20, Matthew Pickering wrote: > > I restarted the service but somethings still appear to be broken. > > On Tue, Jun 1, 2021 at 9:16 AM Shayne Fletcher > wrote: > > > > Seems to be serving again now > > > > On Tue, Jun 1, 2021 at 4:13 PM Vladislav Zav

Re: GitLab downtime

I restarted the service but somethings still appear to be broken. On Tue, Jun 1, 2021 at 9:16 AM Shayne Fletcher wrote: > > Seems to be serving again now > > On Tue, Jun 1, 2021 at 4:13 PM Vladislav Zavialov > wrote: >> >> It is currently down with a 502 error. >> >> - Vlad >> >> > On 1 Jun 202

Re: GitLab downtime

Seems to be serving again now On Tue, Jun 1, 2021 at 4:13 PM Vladislav Zavialov wrote: > It is currently down with a 502 error. > > - Vlad > > > On 1 Jun 2021, at 04:01, Ben Gamari wrote: > > > > Hi all, > > > > I believe gitlab.haskell.org should be back up at this point. There are > > still a

Re: GitLab downtime

It is currently down with a 502 error. - Vlad > On 1 Jun 2021, at 04:01, Ben Gamari wrote: > > Hi all, > > I believe gitlab.haskell.org should be back up at this point. There are > still a few ancillary services (e.g. grafana.gitlab.haskell.org) that I > haven't yet validated but every critica

Re: GitLab downtime

Ben Gamari writes: > Hi all, > Hi all, I believe gitlab.haskell.org should be back up at this point. There are still a few ancillary services (e.g. grafana.gitlab.haskell.org) that I haven't yet validated but every critical should be functional. Do let me know if you find anything amiss. Cheers

Re: GitLab downtime

Richard Eisenberg writes: > GitLab appears to be back up. However, access via ssh tells me > > @@@ > @ WARNING: POSSIBLE DNS SPOOFING DETECTED! @ > @@@ > The ED25519 host

Re: GitLab downtime

GitLab appears to be back up. However, access via ssh tells me @@@ @ WARNING: POSSIBLE DNS SPOOFING DETECTED! @ @@@ The ED25519 host key for gitlab.haskell.org has changed

Re: GitLab downtime

Ben Gamari writes: > Ben Gamari writes: > >> Hi all, >> >> Today I'm going to be working on migrating our GitLab instance to a new >> machine. Starting in likely an hour there will be a few hours of >> downtime while the migration proceeds. I will send an email when the >> downtime begins and co

Re: GitLab downtime

Ben Gamari writes: > Hi all, > > Today I'm going to be working on migrating our GitLab instance to a new > machine. Starting in likely an hour there will be a few hours of > downtime while the migration proceeds. I will send an email when the > downtime begins and concludes. > Hi all, A brief up

Re: GitLab is down: urgent

Davean has resurrected gitlab for now. On Mon, Mar 22, 2021 at 12:31 PM Moritz Angermann < moritz.angerm...@gmail.com> wrote: > It appears as if gitlab went down again, this time since around 4AM UTC on > Monday. > > On Sun, Mar 21, 2021 at 9:49 PM Ben Gamari wrote: > >> Moritz Angermann writes

Re: GitLab is down: urgent

It appears as if gitlab went down again, this time since around 4AM UTC on Monday. On Sun, Mar 21, 2021 at 9:49 PM Ben Gamari wrote: > Moritz Angermann writes: > > > Just a heads up everyone. Gitlab appears down again. This seemed to have > > happened around Sunday, 4AM UTC. > > > > Everyone h

Re: GitLab is down: urgent

Moritz Angermann writes: > Just a heads up everyone. Gitlab appears down again. This seemed to have > happened around Sunday, 4AM UTC. > > Everyone have a blissful Sunday! > It is back up, again. It appears that GitLab's backup retention logic is now either broken or has changed since it is now

Re: GitLab is down: urgent

Just a heads up everyone. Gitlab appears down again. This seemed to have happened around Sunday, 4AM UTC. Everyone have a blissful Sunday! On Sat, 20 Mar 2021 at 6:05 PM, Giorgio Marinelli wrote: > I can also help (~UTC+1), I've a long history and experience in > systems management and enginee

Re: Configuration documentation (Was Re: GitLab is down: urgent)

On Fri, Mar 19, 2021 at 07:08:35PM +, Richard Eisenberg wrote: > > On Mar 19, 2021, at 2:21 PM, Gershom B wrote: > > Cc: ad...@haskell.org which remains (since it was set up over five? > > years ago) the contact address for haskell infra admin stuff. > > How would I learn of that address? Who

Re: GitLab is down: urgent

I can also help (~UTC+1), I've a long history and experience in systems management and engineering. Best, Giorgio Marinelli https://marinelli.dev/cv On Sat, 20 Mar 2021 at 00:31, Moritz Angermann wrote: > > I can try to step up and be backup on the other side of the planet. Ben and I > are alm

Re: GitLab is down: urgent

I can try to step up and be backup on the other side of the planet. Ben and I are almost 12hs apart exactly. On Sat, 20 Mar 2021 at 1:32 AM, Richard Eisenberg wrote: > > > On Mar 19, 2021, at 12:44 PM, howard.b.gol...@gmail.com wrote: > > I would like to help however I can. I already maintain th

Re: Configuration documentation (Was Re: GitLab is down: urgent)

> How would I learn of that address? Who is ad...@haskell.org? In fact, I know you knew this address at one point, because you emailed it asking for help with the haskell symposium website in 2019 :-) But yes, we all learn things and forget them, so documenting them accessibly is important. The

Re: Configuration documentation (Was Re: GitLab is down: urgent)

Thanks, Gershom, for the quick and very illuminating response. > On Mar 19, 2021, at 2:21 PM, Gershom B wrote: > > Cc: ad...@haskell.org which remains (since it was set up over five? > years ago) the contact address for haskell infra admin stuff. How would I learn of that address? Who is ad...@

Re: Configuration documentation (Was Re: GitLab is down: urgent)

I suggest continuing this discussion/effort on the Haskell Discourse at https://discourse.haskell.org/t/documentation-of-haskell-websites-servers-and-their-configurations/2153 . Howard On Fri, 2021-03-19 at 14:21 -0400, Gershom B wrote: > Cc: ad...@haskell.org which remains (since it was set up

Re: Configuration documentation (Was Re: GitLab is down: urgent)

Thanks, Howard! > On Mar 19, 2021, at 2:13 PM, howard.b.gol...@gmail.com wrote: > > I also > will abide by the Haskell Foundation and the haskell.org committee in > arranging this documentation according to their needs and preferences. Thanks for this explicit comment, but I don't think there ar

Configuration documentation (Was Re: GitLab is down: urgent)

Hi Richard, Gershom and Ben, I have access to the server that runs the Haskell wiki. There are other websites on that server as well. I can document them as well. I know that Gershom B. has done most (all?) of the work on that server. I ask him and the haskell.org committee to send me or point me

Re: GitLab is down: urgent

> On Mar 19, 2021, at 12:44 PM, howard.b.gol...@gmail.com wrote: > > I would like to help however I can. I already maintain the Haskell > wiki, and I would like to improve and document its configuration using > devops techniques, preferably consistent with gitlab.haskell.org >

Re: GitLab is down: urgent

Hi Ben, Richard and Davean, I would like to help however I can. I already maintain the Haskell wiki, and I would like to improve and document its configuration using devops techniques, preferably consistent with gitlab.haskell.org. Regards, Howard On Fri, 2021-03-19 at 12:14 -0400, davean wrote:

Re: GitLab is down: urgent

There is the haskell-infrastructure group, who has access. Its knowledge of the peculiarities of each of the very different services that's harder to keep up to date between people. If Ben was hit by a bus it is prepared to be handled. With this diversity and level of manpower though stepping in t

Re: GitLab is down: urgent

Hi Everyone, Didn't there exist the ghc-devops group to talk about and manage those problems/topics? Best, Giorgio On Fri, 19 Mar 2021 at 15:00, Richard Eisenberg wrote: > > Hi Ben, > > Thanks for getting the fix in so quickly. > > However: suppose you were unavailable to do this, due to a we

Re: GitLab is down: urgent

Hi Ben, Thanks for getting the fix in so quickly. However: suppose you were unavailable to do this, due to a well-deserved holiday perhaps. Who else has the credentials and know-how to step in? I feel as if we should have a resource somewhere with a definitive list of critical services and who

Re: GitLab is down: urgent

Simon Peyton Jones via ghc-devs writes: > GHC's GitLab seems to be down. Ben? > (I just get 502's) Everything should now be back to normal. I have sent a post-mortem describing the failure mode and fix. Apologies for the inconvenience! Cheers, - Ben signature.asc Description: PGP signature

Re: GitLab is down: urgent

Simon Peyton Jones via ghc-devs writes: > GHC's GitLab seems to be down. Ben? > (I just get 502's) I am currently working on this. Unfortunately it looks like we yet again ran out of disk space (in part as a result of the upgrade). Will be up within the hour. Cheers, - Ben signature.asc De

Re: GitLab is down: urgent

>From IRC: it appears that some disks on the gitlab machine are full. I don't know who can fix this issue when Ben is away. On Fri, Mar 19, 2021 at 9:35 AM Simon Peyton Jones via ghc-devs < ghc-devs@haskell.org> wrote: > GHC’s GitLab seems to be down. Ben? > > (I just get 502’s) > > Simon > ___

Re: GitLab upgrade soon

502 On Fri, 19 Mar 2021 at 00:05, Ben Gamari wrote: > > Ben Gamari writes: > > > Hi all, > > > > I will be performing a GitLab upgrade starting in approximately one > > hour. While I generally try to do this with more notice and out of > > working hours, in this case there is an exploitable GitL

Re: GitLab upgrade soon

Ben Gamari writes: > Hi all, > > I will be performing a GitLab upgrade starting in approximately one > hour. While I generally try to do this with more notice and out of > working hours, in this case there is an exploitable GitLab vulnerability > that deserves swift action. Thank you for you pati

Re: GitLab down

Richard Eisenberg writes: >> On Oct 23, 2020, at 10:05 AM, Ben Gamari wrote: >> >> GitLab is back up and notification email has been restored. > > I'm seeing new emails -- thanks. Should we expect to get the notifications > that weren't delivered yesterday? > I'm afraid not. It looks like GitL

Re: GitLab down

> On Oct 23, 2020, at 10:05 AM, Ben Gamari wrote: > > GitLab is back up and notification email has been restored. I'm seeing new emails -- thanks. Should we expect to get the notifications that weren't delivered yesterday? Thanks! Richard___ ghc-de

Re: GitLab down

Ben Gamari writes: > Hi all, > > GitLab will be down for a bit while I do a bit of maintenance. > GitLab is back up and notification email has been restored. Cheers, - Ben signature.asc Description: PGP signature ___ ghc-devs mailing list ghc-devs@h

Re: GitLab e-mails: down for everyone, or just me?

I, too, have received no notifications at all from GitLab. Richard > On Oct 22, 2020, at 7:34 AM, Ryan Scott wrote: > > Since yesterday, I haven't been receiving any e-mail notifications from > GitLab. Are other people having this problem too, or is it a problem on my > end? > > Ryan S. > __

Re: GitLab status

Ryan Scott writes: > Just as an FYI, there appears to be some data loss from this migration. For > example, I pushed a commit to !3536 [1] that appears to have been dropped, > leading to confusion here [2]. To make things worse, I never received an > e-mail notification for this comment—I only di

Re: GitLab status

Just as an FYI, there appears to be some data loss from this migration. For example, I pushed a commit to !3536 [1] that appears to have been dropped, leading to confusion here [2]. To make things worse, I never received an e-mail notification for this comment—I only discovered it by chance. I als

Re: GitLab status

Ben Gamari writes: > Ben Gamari writes: > >> Hi everyone, >> >> As you may have noticed, yesterday was marked by rather consistent CI >> failures. I believe I have now fixed the root cause but do let me know >> if you see any further issues. >> >> Below I have included a brief post-mortem descri

Re: GitLab status

Ben Gamari writes: > Hi everyone, > > As you may have noticed, yesterday was marked by rather consistent CI > failures. I believe I have now fixed the root cause but do let me know > if you see any further issues. > > Below I have included a brief post-mortem describing the incident and > what we

RE: Gitlab is stuck

Simon Peyton Jones writes: > All good now? > As noted earlier, the safe answer is "no". It appears that our storage provider is having some trouble. I'm so far unsure of whether this is a temporary problem or something more sinister. Cheers, - Ben signature.asc Description: PGP signature

Re: Gitlab corrupt

Simon Peyton Jones via ghc-devs writes: > Ben > Something is amiss. "corrupt" sounds bad! > Simon > Indeed something seems to have gone awry here. I'm currently working on getting to the bottom of it. Cheers, - Ben signature.asc Description: PGP signature _

RE: Gitlab is stuck

All good now? | -Original Message- | From: Ben Gamari | Sent: 19 June 2020 14:37 | To: Simon Peyton Jones ; GHC developers | Subject: Re: Gitlab is stuck | | Simon Peyton Jones via ghc-devs writes: | | > Something is badly wrong with gitlab. I'm trying to push a bra

Re: Gitlab is stuck

Simon Peyton Jones via ghc-devs writes: > Something is badly wrong with gitlab. I'm trying to push a branch. Is some > disk full? > I am fully stalled. I am rebooting the machine; indeed something is amiss here. Cheers, - Ben signature.asc Description: PGP signature __

  1   2   3   >