Re: GitLab upgrade later today

[Ben Gamari]

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
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab upgrade later today

[Ben Gamari]

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.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab approval

[Bryan Richter via ghc-devs]

Ahhh yes, that explains it. You need (and have requested) the Developer
role on the GHC project.

I've approved the request, so you should be able to do those things now.

On Thu, 10 Aug 2023 at 09:19, cydparser  wrote:

> I have a GitLab account, but am unable to perform basic actions like
> fixing broken links on wiki pages or adding a label to a MR that I created.
> The GHC project overview has a link with "Withdraw Access Request" at the
> top, so perhaps I need access rather than 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: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://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab approval

[cydparser]

I have a GitLab account, but am unable to perform basic actions like fixing
broken links on wiki pages or adding a label to a MR that I created. The
GHC project overview has a link with "Withdraw Access Request" at the top,
so perhaps I need access rather than 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: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://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab approval

[Ben Gamari]

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://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab approval

[cydparser]

Can a GitLab admin please approve my account (@cydparser). Thanks!
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

New spurious failure bot is running on GitLab

[Bryan Richter via ghc-devs]

Today I've deployed a new version of my retry service. I think I've worked
out most of the kinks, so I'm going to leave it running overnight and see
how it goes.

In the worst case, it might crash and die, in which case spurious failures
will not get retried until I come back and fix it tomorrow morning, Europe
time.

In the best case, the service will just keep doing what the old one did,
with two improvements:

1. If the same job keeps failing, it will give up retries.
2. If sending a retry command to GitLab itself fails, those will also be
retried a few times.

-Bryan

"Who retries the retryer?" - Juvenal, probably
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab CI happenings in July

[Bryan Richter via ghc-devs]

Hello,

This is the first (and, perhaps, last[1]) monthly update on GitLab CI. This
month in particular deserves its own little email for the following reasons:

1. Some of the Darwin runners recently spontaneously self-upgraded,
introducing toolchain changes that broke CI. All the fixes are now on GHC's
master branch. This leaves us with two choices:

A) Re-enable the affected runners now. All current patches will have a 50%
of failing CI because the old problems are still present. Users (you) can
rebase your patches to avoid this problem.

B) Wait before re-enabling the runners. All in-flight MRs have a better
chance of getting green CI and/or organically getting rebased for other
reasons. However, Darwin capacity would remain at 50% for longer, slowing
down all pipelines.

My current plan is to wait one week before re-enabling the runners, but
ultimately it's not my call. Opinions welcome.

2. I will be on vacation from July 17 to July 28 (weeks 29 and 30). Please
tell Marge to be good while I am away.

3. GitLab was recently upgraded. Please do not be alarmed by any UI changes.

Enjoy!

-Bryan

[1]: Intuitively, I like the idea of giving monthly updates about GitLab
CI. But I don't know if it will be practical or valuable. I'll take a look
in a month to see if there's anything notable to write about again.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab upgraded

[Ben Gamari]

Hi all,

This evening (EST) I performed a quick upgrade of gitlab.haskell.org.

As a result, you will notice that the UI has changed quite a bit. This is
due to a beta redesign of GitLab's navigation scheme. While I've found
it relatively unobjectionable (and seemingly a bit more snappier),
your mileage may vary. If you find the redesign particularly onerous,
you can (for now) disable it by toggling the "New navigation" slider in
your "user" menu (accessed by clicking on your avatar icon in the
sidebar on the left).

If you do find that reverting is necessary, please do raise an issue
with upstream as I suspect that upstream will commit to the redesign in
the next few releases.

As always, if you find something isn't working as you would expect,
don't hesitate to reach out.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: SSH on Gitlab

[Bryan Richter via ghc-devs]

Ah - my bet is that the hospital's IT department were simply blocking ssh
as a "better safe than sorry" infosec policy.

On Tue, 27 Jun 2023 at 12:37, Simon Peyton Jones <
simon.peytonjo...@gmail.com> wrote:

> Thanks for following up.
>
> I came home from hospital, and it was fine at home.  Maybe there was
> something strange in their Wifi.   If I was there for longer I'd have had
> to investigate more (somehow) but it was a thankfully brief stay.
>
> Simon
>
> On Tue, 27 Jun 2023 at 07:29, Bryan Richter 
> wrote:
>
>> Hi Simon,
>>
>> Did this, in fact, work itself out?
>>
>> On Thu, 22 Jun 2023 at 18:43, Ben Gamari  wrote:
>>
>>> Simon Peyton Jones  writes:
>>>
>>> > Is SSH working on gitlab.haskell.org?  I'm getting this
>>> >
>>> > simonpj@CDW-8FABODHF0V5:~$ ssh -v g...@gitlab.haskell.org
>>> > OpenSSH_8.2p1 Ubuntu-4, OpenSSL 1.1.1f  31 Mar 2020
>>> > debug1: Reading configuration data /home/simonpj/.ssh/config
>>> > debug1: Reading configuration data /etc/ssh/ssh_config
>>> > debug1: /etc/ssh/ssh_config line 19: include
>>> /etc/ssh/ssh_config.d/*.conf
>>> > matched no files
>>> > debug1: /etc/ssh/ssh_config line 21: Applying options for *
>>> > debug1: Connecting to gitlab.haskell.org [145.40.64.137] port 22.
>>> > debug1: Connection established.
>>> > debug1: identity file /home/simonpj/.ssh/id_rsa type 0
>>> > debug1: identity file /home/simonpj/.ssh/id_rsa-cert type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_dsa type 1
>>> > debug1: identity file /home/simonpj/.ssh/id_dsa-cert type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_ecdsa type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_ecdsa-cert type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk-cert type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_ed25519 type 3
>>> > debug1: identity file /home/simonpj/.ssh/id_ed25519-cert type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_ed25519_sk type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_ed25519_sk-cert type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_xmss type -1
>>> > debug1: identity file /home/simonpj/.ssh/id_xmss-cert type -1
>>> > debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4
>>> >
>>> > At this point it hangs.  Stackoverflow suggests
>>> > <
>>> https://superuser.com/questions/1374076/what-does-it-mean-if-ssh-hangs-after-connection-established
>>> >a
>>> > server fault.  But I'm on a new WLAN so I suppose there could be some
>>> > bizarre filtering?
>>> >
>>> I suspect this may be a filtering issue. Like Tom, I am able to connect
>>> without issue. A Wireshark trace [1] may help shed light on the
>>> situation. Happy to have a call to debug if this would be helpful.
>>>
>>> Cheers,
>>>
>>> - Ben
>>>
>>>
>>> [1] https://www.wireshark.org/
>>> ___
>>> ghc-devs mailing list
>>> ghc-devs@haskell.org
>>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>>>
>>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: SSH on Gitlab

[Simon Peyton Jones]

Thanks for following up.

I came home from hospital, and it was fine at home.  Maybe there was
something strange in their Wifi.   If I was there for longer I'd have had
to investigate more (somehow) but it was a thankfully brief stay.

Simon

On Tue, 27 Jun 2023 at 07:29, Bryan Richter 
wrote:

> Hi Simon,
>
> Did this, in fact, work itself out?
>
> On Thu, 22 Jun 2023 at 18:43, Ben Gamari  wrote:
>
>> Simon Peyton Jones  writes:
>>
>> > Is SSH working on gitlab.haskell.org?  I'm getting this
>> >
>> > simonpj@CDW-8FABODHF0V5:~$ ssh -v g...@gitlab.haskell.org
>> > OpenSSH_8.2p1 Ubuntu-4, OpenSSL 1.1.1f  31 Mar 2020
>> > debug1: Reading configuration data /home/simonpj/.ssh/config
>> > debug1: Reading configuration data /etc/ssh/ssh_config
>> > debug1: /etc/ssh/ssh_config line 19: include
>> /etc/ssh/ssh_config.d/*.conf
>> > matched no files
>> > debug1: /etc/ssh/ssh_config line 21: Applying options for *
>> > debug1: Connecting to gitlab.haskell.org [145.40.64.137] port 22.
>> > debug1: Connection established.
>> > debug1: identity file /home/simonpj/.ssh/id_rsa type 0
>> > debug1: identity file /home/simonpj/.ssh/id_rsa-cert type -1
>> > debug1: identity file /home/simonpj/.ssh/id_dsa type 1
>> > debug1: identity file /home/simonpj/.ssh/id_dsa-cert type -1
>> > debug1: identity file /home/simonpj/.ssh/id_ecdsa type -1
>> > debug1: identity file /home/simonpj/.ssh/id_ecdsa-cert type -1
>> > debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk type -1
>> > debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk-cert type -1
>> > debug1: identity file /home/simonpj/.ssh/id_ed25519 type 3
>> > debug1: identity file /home/simonpj/.ssh/id_ed25519-cert type -1
>> > debug1: identity file /home/simonpj/.ssh/id_ed25519_sk type -1
>> > debug1: identity file /home/simonpj/.ssh/id_ed25519_sk-cert type -1
>> > debug1: identity file /home/simonpj/.ssh/id_xmss type -1
>> > debug1: identity file /home/simonpj/.ssh/id_xmss-cert type -1
>> > debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4
>> >
>> > At this point it hangs.  Stackoverflow suggests
>> > <
>> https://superuser.com/questions/1374076/what-does-it-mean-if-ssh-hangs-after-connection-established
>> >a
>> > server fault.  But I'm on a new WLAN so I suppose there could be some
>> > bizarre filtering?
>> >
>> I suspect this may be a filtering issue. Like Tom, I am able to connect
>> without issue. A Wireshark trace [1] may help shed light on the
>> situation. Happy to have a call to debug if this would be helpful.
>>
>> Cheers,
>>
>> - Ben
>>
>>
>> [1] https://www.wireshark.org/
>> ___
>> ghc-devs mailing list
>> ghc-devs@haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>>
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: SSH on Gitlab

[Bryan Richter via ghc-devs]

Hi Simon,

Did this, in fact, work itself out?

On Thu, 22 Jun 2023 at 18:43, Ben Gamari  wrote:

> Simon Peyton Jones  writes:
>
> > Is SSH working on gitlab.haskell.org?  I'm getting this
> >
> > simonpj@CDW-8FABODHF0V5:~$ ssh -v g...@gitlab.haskell.org
> > OpenSSH_8.2p1 Ubuntu-4, OpenSSL 1.1.1f  31 Mar 2020
> > debug1: Reading configuration data /home/simonpj/.ssh/config
> > debug1: Reading configuration data /etc/ssh/ssh_config
> > debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf
> > matched no files
> > debug1: /etc/ssh/ssh_config line 21: Applying options for *
> > debug1: Connecting to gitlab.haskell.org [145.40.64.137] port 22.
> > debug1: Connection established.
> > debug1: identity file /home/simonpj/.ssh/id_rsa type 0
> > debug1: identity file /home/simonpj/.ssh/id_rsa-cert type -1
> > debug1: identity file /home/simonpj/.ssh/id_dsa type 1
> > debug1: identity file /home/simonpj/.ssh/id_dsa-cert type -1
> > debug1: identity file /home/simonpj/.ssh/id_ecdsa type -1
> > debug1: identity file /home/simonpj/.ssh/id_ecdsa-cert type -1
> > debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk type -1
> > debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk-cert type -1
> > debug1: identity file /home/simonpj/.ssh/id_ed25519 type 3
> > debug1: identity file /home/simonpj/.ssh/id_ed25519-cert type -1
> > debug1: identity file /home/simonpj/.ssh/id_ed25519_sk type -1
> > debug1: identity file /home/simonpj/.ssh/id_ed25519_sk-cert type -1
> > debug1: identity file /home/simonpj/.ssh/id_xmss type -1
> > debug1: identity file /home/simonpj/.ssh/id_xmss-cert type -1
> > debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4
> >
> > At this point it hangs.  Stackoverflow suggests
> > <
> https://superuser.com/questions/1374076/what-does-it-mean-if-ssh-hangs-after-connection-established
> >a
> > server fault.  But I'm on a new WLAN so I suppose there could be some
> > bizarre filtering?
> >
> I suspect this may be a filtering issue. Like Tom, I am able to connect
> without issue. A Wireshark trace [1] may help shed light on the
> situation. Happy to have a call to debug if this would be helpful.
>
> Cheers,
>
> - Ben
>
>
> [1] https://www.wireshark.org/
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: SSH on Gitlab

[Ben Gamari]

Simon Peyton Jones  writes:

> Is SSH working on gitlab.haskell.org?  I'm getting this
>
> simonpj@CDW-8FABODHF0V5:~$ ssh -v g...@gitlab.haskell.org
> OpenSSH_8.2p1 Ubuntu-4, OpenSSL 1.1.1f  31 Mar 2020
> debug1: Reading configuration data /home/simonpj/.ssh/config
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf
> matched no files
> debug1: /etc/ssh/ssh_config line 21: Applying options for *
> debug1: Connecting to gitlab.haskell.org [145.40.64.137] port 22.
> debug1: Connection established.
> debug1: identity file /home/simonpj/.ssh/id_rsa type 0
> debug1: identity file /home/simonpj/.ssh/id_rsa-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_dsa type 1
> debug1: identity file /home/simonpj/.ssh/id_dsa-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_ecdsa type -1
> debug1: identity file /home/simonpj/.ssh/id_ecdsa-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk type -1
> debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_ed25519 type 3
> debug1: identity file /home/simonpj/.ssh/id_ed25519-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_ed25519_sk type -1
> debug1: identity file /home/simonpj/.ssh/id_ed25519_sk-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_xmss type -1
> debug1: identity file /home/simonpj/.ssh/id_xmss-cert type -1
> debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4
>
> At this point it hangs.  Stackoverflow suggests
> a
> server fault.  But I'm on a new WLAN so I suppose there could be some
> bizarre filtering?
>
I suspect this may be a filtering issue. Like Tom, I am able to connect
without issue. A Wireshark trace [1] may help shed light on the
situation. Happy to have a call to debug if this would be helpful.

Cheers,

- Ben


[1] https://www.wireshark.org/


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: SSH on Gitlab

[Bryan Richter via ghc-devs]

Hi Simon,

I'm on vacation this week and can't help or attempt to reproduce. I
suspect, however, this is going to get better on its own. Any evidence for
or against intermittent network issues that anyone can provide, now or any
other time, would help me look into this later. For example, are there
correlations between ssh and website issues? Does CI have network issues at
the same time? Etc.

Good luck.

On Thu, 22 Jun 2023, 13.15 Simon Peyton Jones, 
wrote:

> Is SSH working on gitlab.haskell.org?  I'm getting this
>
> simonpj@CDW-8FABODHF0V5:~$ ssh -v g...@gitlab.haskell.org
> OpenSSH_8.2p1 Ubuntu-4, OpenSSL 1.1.1f  31 Mar 2020
> debug1: Reading configuration data /home/simonpj/.ssh/config
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf
> matched no files
> debug1: /etc/ssh/ssh_config line 21: Applying options for *
> debug1: Connecting to gitlab.haskell.org [145.40.64.137] port 22.
> debug1: Connection established.
> debug1: identity file /home/simonpj/.ssh/id_rsa type 0
> debug1: identity file /home/simonpj/.ssh/id_rsa-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_dsa type 1
> debug1: identity file /home/simonpj/.ssh/id_dsa-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_ecdsa type -1
> debug1: identity file /home/simonpj/.ssh/id_ecdsa-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk type -1
> debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_ed25519 type 3
> debug1: identity file /home/simonpj/.ssh/id_ed25519-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_ed25519_sk type -1
> debug1: identity file /home/simonpj/.ssh/id_ed25519_sk-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_xmss type -1
> debug1: identity file /home/simonpj/.ssh/id_xmss-cert type -1
> debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4
>
> At this point it hangs.  Stackoverflow suggests
> a
> server fault.  But I'm on a new WLAN so I suppose there could be some
> bizarre filtering?
>
> Thanks
>
> Simon
>
>
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: SSH on Gitlab

[Tom Ellis]

FWIW if I try the same command I get all the way through to a normal
exit (which I guess is expected since you're not supposed to be able
to actually obtain a shell via ssh!) so I guess the problem is
specific to you, Simon.

Tom



OpenSSH_8.4p1 Debian-5+deb11u1, OpenSSL 1.1.1n  15 Mar 2022
debug1: Reading configuration data /home/tom/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to gitlab.haskell.org [2604:1380:61:2300::1] port 22.
debug1: Connection established.
debug1: identity file 
debug1: Local version string SSH-2.0-OpenSSH_8.4p1 Debian-5+deb11u1
debug1: Remote protocol version 2.0, remote software version OpenSSH_9.1
debug1: match: OpenSSH_9.1 pat OpenSSH* compat 0x0400
debug1: Authenticating to gitlab.haskell.org:22 as 'git'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-ed25519 
SHA256:/dI7zsBRZNPB+0TqskF7rSaZ/LhQw0cF4c5W+4uMlRo
debug1: Host 'gitlab.haskell.org' is known and matches the ED25519 host key.
debug1: Found key in 
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: Will attempt key: 
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: 
server-sig-algs=
debug1: kex_input_ext_info: publickey-hostbo...@openssh.com (unrecognised)
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: 
publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering public key: 
debug1: Authentications that can continue: 
publickey,password,keyboard-interactive
debug1: Offering public key: 
debug1: Server accepts key: 
debug1: Authentication succeeded (publickey).
Authenticated to gitlab.haskell.org ([2604:1380:61:2300::1]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessi...@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_global_request: rtype hostkeys...@openssh.com want_reply 0
debug1: Remote: /var/gitlab/state/home/.ssh/authorized_keys:857: key options: 
command user-rc
debug1: Remote: /var/gitlab/state/home/.ssh/authorized_keys:857: key options: 
command user-rc
debug1: Sending environment.
debug1: Sending env LANG = en_GB.UTF-8
PTY allocation request failed on channel 0
Welcome to GitLab, @tomjaguarpaw1!
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype e...@openssh.com reply 0
debug1: channel 0: free: client-session, nchannels 1
Connection to gitlab.haskell.org closed.
Transferred: sent 3296, received 2832 bytes, in 0.4 seconds
Bytes per second: sent 9134.7, received 7848.7
debug1: Exit status 0



On Thu, Jun 22, 2023 at 11:15:28AM +0100, Simon Peyton Jones wrote:
> Is SSH working on gitlab.haskell.org?  I'm getting this
> 
> simonpj@CDW-8FABODHF0V5:~$ ssh -v g...@gitlab.haskell.org
> OpenSSH_8.2p1 Ubuntu-4, OpenSSL 1.1.1f  31 Mar 2020
> debug1: Reading configuration data /home/simonpj/.ssh/config
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf
> matched no files
> debug1: /etc/ssh/ssh_config line 21: Applying options for *
> debug1: Connecting to gitlab.haskell.org [145.40.64.137] port 22.
> debug1: Connection established.
> debug1: identity file /home/simonpj/.ssh/id_rsa type 0
> debug1: identity file /home/simonpj/.ssh/id_rsa-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_dsa type 1
> debug1: identity file /home/simonpj/.ssh/id_dsa-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_ecdsa type -1
> debug1: identity file /home/simonpj/.ssh/id_ecdsa-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk type -1
> debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_ed25519 type 3
> debug1: identity file /home/simonpj/.ssh/id_ed25519-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_ed25519_sk type -1
> debug1: identity file /home/simonpj/.ssh/id_ed25519_sk-cert type -1
> debug1: identity file /home/simonpj/.ssh/id_xmss type -1
> debug1: identity file /home/simonpj/.ssh/id_xmss-cert type -1
> debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4
> 
> At this point it hangs.  Stackoverflow suggests
> <https://superuser.co

SSH on Gitlab

[Simon Peyton Jones]

Is SSH working on gitlab.haskell.org?  I'm getting this

simonpj@CDW-8FABODHF0V5:~$ ssh -v g...@gitlab.haskell.org
OpenSSH_8.2p1 Ubuntu-4, OpenSSL 1.1.1f  31 Mar 2020
debug1: Reading configuration data /home/simonpj/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf
matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to gitlab.haskell.org [145.40.64.137] port 22.
debug1: Connection established.
debug1: identity file /home/simonpj/.ssh/id_rsa type 0
debug1: identity file /home/simonpj/.ssh/id_rsa-cert type -1
debug1: identity file /home/simonpj/.ssh/id_dsa type 1
debug1: identity file /home/simonpj/.ssh/id_dsa-cert type -1
debug1: identity file /home/simonpj/.ssh/id_ecdsa type -1
debug1: identity file /home/simonpj/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/simonpj/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/simonpj/.ssh/id_ed25519 type 3
debug1: identity file /home/simonpj/.ssh/id_ed25519-cert type -1
debug1: identity file /home/simonpj/.ssh/id_ed25519_sk type -1
debug1: identity file /home/simonpj/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/simonpj/.ssh/id_xmss type -1
debug1: identity file /home/simonpj/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4

At this point it hangs.  Stackoverflow suggests
a
server fault.  But I'm on a new WLAN so I suppose there could be some
bizarre filtering?

Thanks

Simon
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GHC GitLab change to login: disabling OAuth via GitHub

[Bryan Richter via ghc-devs]

Hi Jakob, thanks for the confirmation.

I've had one report that the password reset email ended up in the spam
folder, so be on the lookout for that.

-Bryan

On Sun, 7 May 2023 at 15:51, Jakob Brünker  wrote:

> Hi,
>
> for what it's worth, as someone who has been using GitHub OAuth, it looks
> like using the password reset functionality with one's github email address
> is enough to be able to log in.
>
> Best,
> Jakob
>
> On Sun, May 7, 2023 at 12:08 PM Bryan Richter via ghc-devs <
> ghc-devs@haskell.org> wrote:
>
>> Hi folks,
>>
>> Spammers have been abusing GitHub OAuth to create accounts on
>> gitlab.haskell.org and post spam.
>>
>> Due to team resources, the only good way to stop spammers right now is to
>> manually approve each new user. GitHub OAuth defeats that by automatically
>> approving new users.
>>
>> So, sadly, I have disabled GitHub OAuth for the time being. If you used
>> it to sign up and have trouble logging in now, one of us admins can help
>> you out.
>>
>> -Bryan
>> ___
>> ghc-devs mailing list
>> ghc-devs@haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>>
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GHC GitLab change to login: disabling OAuth via GitHub

[Jakob Brünker]

Hi,

for what it's worth, as someone who has been using GitHub OAuth, it looks
like using the password reset functionality with one's github email address
is enough to be able to log in.

Best,
Jakob

On Sun, May 7, 2023 at 12:08 PM Bryan Richter via ghc-devs <
ghc-devs@haskell.org> wrote:

> Hi folks,
>
> Spammers have been abusing GitHub OAuth to create accounts on
> gitlab.haskell.org and post spam.
>
> Due to team resources, the only good way to stop spammers right now is to
> manually approve each new user. GitHub OAuth defeats that by automatically
> approving new users.
>
> So, sadly, I have disabled GitHub OAuth for the time being. If you used it
> to sign up and have trouble logging in now, one of us admins can help you
> out.
>
> -Bryan
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GHC GitLab change to login: disabling OAuth via GitHub

[Bryan Richter via ghc-devs]

Hi folks,

Spammers have been abusing GitHub OAuth to create accounts on
gitlab.haskell.org and post spam.

Due to team resources, the only good way to stop spammers right now is to
manually approve each new user. GitHub OAuth defeats that by automatically
approving new users.

So, sadly, I have disabled GitHub OAuth for the time being. If you used it
to sign up and have trouble logging in now, one of us admins can help you
out.

-Bryan
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab partial outage - attempting to mitigate

[Ben Gamari]

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 signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab partial outage - attempting to mitigate

[Ben Gamari]

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 /nix is located on the small system drive. We
> should really address this although moving /nix is sadly not easy and
> will certainly require downtime.
>
In the meantime, I have significantly reduced the number of snapshots
retained in the root dataset. This brought disk usage down from 70% to
12%, which should keep us afloat for a long while.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab partial outage - attempting to mitigate

[Brandon Allbery]

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 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 system drive. We
> should really address this although moving /nix is sadly not easy and
> will certainly require downtime.
>
> Cheers,
>
> - Ben
>
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs



-- 
brandon s allbery kf8nh
allber...@gmail.com
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab partial outage - attempting to mitigate

[Ben Gamari]

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 system drive. We
should really address this although moving /nix is sadly not easy and
will certainly require downtime.

Cheers,

- Ben



signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab partial outage - attempting to mitigate

[Bryan Richter via ghc-devs]

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=now-7d=now=30m
* High-frequency repetition of the system log message
"systemd-journald[1622008]: Failed to open runtime journal: Device or
resource busy"
* ~50% failure rate connecting to the server with ssh

None of those are happening anymore.

-Bryan

On Mon, 20 Mar 2023 at 14:41, Bryan Richter 
wrote:

> I am seeing a few different problems with the GitLab server right now. I
> am gonna try to mitigate the issues, so the server might be unavailable for
> a few short periods.
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab partial outage - attempting to mitigate

[Bryan Richter via ghc-devs]

I am seeing a few different problems with the GitLab server right now. I am
gonna try to mitigate the issues, so the server might be unavailable for a
few short periods.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: DKIM failures for gitlab mail

[Viktor Dukhovni]

On Mon, Jan 23, 2023 at 03:41:21PM +0100, Joachim Breitner wrote:
> Hi Ben,
> 
> gentle reminder about this issue? I’m worried I (and maybe others) are
> going to miss gitlab notifications.

A recent gitlab notice has:

Received: by gitlab.haskell.org (Postfix, from userid 165)
id AF9E627CA9; Mon, 16 Jan 2023 20:50:59 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gitlab.haskell.org;
s=mail; t=1673920259;
bh=bezCH96kI1N9pklJv6GEpVDADij1+8Q/zwCT65Djz/4=;
h=Date:From:Reply-To:To:Subject:List-Id;
b=L7ikqNV+Hn0OZzM9AH+rLIvP5P9COe8/zuP7bmSsMJ50kFJ2a7gJy4cbxoX83bNqU
oBQV78j6nIFV/SRgbaF9vQciNBzWu1GNACMGaqVMVjTBki93xw/hvMv8JDIhAdAYaV
da96BBtxrTDoDUtFBtYlb5n361TqIDHXHkCqE5Dc=

The DKIM data in DNS is:

$ dig +short +nosplit -t txt mail._domainkey.gitlab.haskell.org
"v=DKIM1; k=rsa; 
p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDiTJ9J8+wWWFRzHjjr5CCbOx33rZaDH2PQsQtTLwOPVZDTSjz8pwUuyQ4s+Xxq6f6UEEAIo/8ZHySJqXG6HN3b6/Gq2SwnE2xLk307gcWzZgyF/9UM5SpcJ46VxYPu2spBQSWhDnRbp849ZouuY/orKT/HMb/9xow25KwWbAyh8wIDAQAB"

Putting it together:

$ echo 
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDiTJ9J8+wWWFRzHjjr5CCbOx33rZaDH2PQsQtTLwOPVZDTSjz8pwUuyQ4s+Xxq6f6UEEAIo/8ZHySJqXG6HN3b6/Gq2SwnE2xLk307gcWzZgyF/9UM5SpcJ46VxYPu2spBQSWhDnRbp849ZouuY/orKT/HMb/9xow25KwWbAyh8wIDAQAB
 |
openssl base64 -A -d |
openssl pkey -pubin -inform DER -out /tmp/pkey.pem

$ openssl base64 -d <<-\EOF > /tmp/sig.dat
L7ikqNV+Hn0OZzM9AH+rLIvP5P9COe8/zuP7bmSsMJ50kFJ2a7gJy4cbxoX83bNq
UoBQV78j6nIFV/SRgbaF9vQciNBzWu1GNACMGaqVMVjTBki93xw/hvMv8JDIhAdA
YaVda96BBtxrTDoDUtFBtYlb5n361TqIDHXHkCqE5Dc=
EOF

$ openssl pkeyutl -pubin -inkey /tmp/pkey.pem \
-encrypt -pkeyopt rsa_padding_mode:none \
-in /tmp/sig.dat -hexdump

 - 52 90 e5 01 80 fa 77 53-b3 19 97 16 33 70 1e 29   R.wS3p.)
0010 - 7e 7b cf 5c a4 51 b2 eb-7c fa 88 dc ce 92 b2 ac   ~{.\.Q..|...
0020 - 4f 86 d4 f1 32 83 55 0a-0b c0 49 92 a3 4a 54 47   O...2.U...I..JTG
0030 - dc 6b 5d bd 2c 1e 5d 85-cf f4 4f c8 3c c5 3f bd   .k].,.]...O.<.?.
0040 - 9d 56 29 a2 b5 dc 94 13-50 c3 28 23 0c a0 64 0b   .V).P.(#..d.
0050 - 0e 99 96 4a 0f b4 36 1a-3a d6 ff 6f 50 00 1a 38   ...J..6.:..oP..8
0060 - 09 34 75 a6 d5 29 da 80-7c c1 bd 77 c4 a3 01 32   .4u..)..|..w...2
0070 - d1 16 b4 8f 6c 3d fd a4-25 8d 53 2b 64 9c d8 ed   l=..%.S+d...

We see that the RSA public key operation does not produce a valid PKCS#1
padded block, so most likely an outdated key is published in DNS, or the
wrong "selector" ("s=" value, currently "mail") was added to the DKIM
signature header (if the correct key is published under some other
selector).

-- 
Viktor.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: DKIM failures for gitlab mail

[Joachim Breitner]

Hi Ben,

gentle reminder about this issue? I’m worried I (and maybe others) are
going to miss gitlab notifications.

Cheers,
Joachim

Am Donnerstag, dem 01.12.2022 um 10:21 +0200 schrieb Bryan Richter via
ghc-devs:
> Thanks for noticing, Joachim!
> 
> Ben Gamari is still the primary contact for GitLab configuration...
> Ben, maybe you know something about this?
> 
> On Wed, Nov 30, 2022 at 7:12 PM Viktor Dukhovni  
> wrote:
> > 
> > On Wed, Nov 30, 2022 at 05:33:44PM +0100, Joachim Breitner wrote:
> > 
> > > I noticed that a small number of Gitlab notification emails end up in
> > > my spamfilter. While there is not much you can do about triggering some
> > > bayesian style spam filter at my email provider (mailbox.org), I did
> > > notice this in the headers:
> > > 
> > > X-Spam-Status: No, score=2.704 tagged_above=2 required=6
> > > tests=[DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HS_RSPAMD_10_11=2.5,
> > > HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001,
> > > URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
> > > Authentication-Results: spamfilter01.heinlein-hosting.de (amavisd-new);
> > > dkim=fail (1024-bit key) reason="fail (bad RSA signature)"
> > > header.d=gitlab.haskell.org
> > > DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
> > > d=gitlab.haskell.org;
> > > s=mail; t=1669733134;
> > > bh=D0NUcHiskEnwSP99umP3zo8Fz8fl74OgAJ8NRDKCsp4=;
> > > h=Date:From:Reply-To:To:In-Reply-To:References:Subject:List-Id:
> > >  List-Unsubscribe;
> > > 
> > > b=R+WMLfhRZZdYxMd6K6w+iodDe8EHzwONNArNyboqsU5NnafPRhKZ1UeGxO/BCMvEK
> > >  
> > > M7XHRRrBsPfRYpTph7xSGY427KGXieASVg1GDhAiwKSLBCiqDdkBaoJLLUIfUD02NS
> > >  ouI3tvQ9mddNdaEK7retq8N+29hzs/ezf9cpgy+Q=
> > 
> > Indeed the signature in "b=" was not made by the key at
> > mail._domainkey.gitlab.haskell.org.  Running the below:
> > 
> > sig=$(
> > printf "%s\n%s\n%s\n" \
> > 
> > R+WMLfhRZZdYxMd6K6w+iodDe8EHzwONNArNyboqsU5NnafPRhKZ1UeGxO/BCMvE \
> > 
> > KM7XHRRrBsPfRYpTph7xSGY427KGXieASVg1GDhAiwKSLBCiqDdkBaoJLLUIfUD0 \
> > 2NSouI3tvQ9mddNdaEK7retq8N+29hzs/ezf9cpgy+Q=
> > )
> > 
> > pkey=$(
> > dig +short -t txt mail._domainkey.gitlab.haskell.org |
> > perl -MMIME::Base64 -ne '
> > /^"v=DKIM1;/ or next;
> > print decode_base64($1) if m{;\s*p=(\S+?)(?:;|$)}
> > ' |
> > openssl pkey -pubin -inform DER
> > )
> > 
> > openssl rsautl -raw -encrypt -pubin \
> > -inkey <( printf "%s\n" "$pkey" ) \
> > -in <(printf "%s\n" "$sig" | openssl base64 -d) |
> > xxd -p
> > 
> > the output is:
> > 
> > 509bfc93a492f1b5328308e51624d9a7ed1378861f577b11413c5034bc0c
> > 673d61660434d4bc30844e7648da0f9605923805973a313a8c3bc82215cc
> > ac447e47551087c544a0592ac3ae48474584bad7d9ca5b850a67493a7977
> > d28aaa3a9a7580d165dc4f31ff484bdbc40e94a2be1750e71c51c555b5c1
> > 6bc051947bb07ae4
> > 
> > Which is not a PKCS#1.5 padded signature block.  So either the
> > "b=" value was corrupted in transit, or it was signed by a key
> > that is different from what is published in DNS.
> > 
> > > but maybe Postfix  is not using the right key?
> > 
> > Strictly speaking that's not Postfix itself, but some DKIM milter, but
> > nits aside, more likely a stale public key is published in DNS.
> > 
> > --
> > Viktor.
> > ___
> > ghc-devs mailing list
> > ghc-devs@haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

-- 
Joachim Breitner
  m...@joachim-breitner.de
  http://www.joachim-breitner.de/

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: DKIM failures for gitlab mail

[Bryan Richter via ghc-devs]

Thanks for noticing, Joachim!

Ben Gamari is still the primary contact for GitLab configuration...
Ben, maybe you know something about this?

On Wed, Nov 30, 2022 at 7:12 PM Viktor Dukhovni  wrote:
>
> On Wed, Nov 30, 2022 at 05:33:44PM +0100, Joachim Breitner wrote:
>
> > I noticed that a small number of Gitlab notification emails end up in
> > my spamfilter. While there is not much you can do about triggering some
> > bayesian style spam filter at my email provider (mailbox.org), I did
> > notice this in the headers:
> >
> > X-Spam-Status: No, score=2.704 tagged_above=2 required=6
> > tests=[DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HS_RSPAMD_10_11=2.5,
> > HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001,
> > URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
> > Authentication-Results: spamfilter01.heinlein-hosting.de (amavisd-new);
> > dkim=fail (1024-bit key) reason="fail (bad RSA signature)"
> > header.d=gitlab.haskell.org
> > DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
> > d=gitlab.haskell.org;
> > s=mail; t=1669733134;
> > bh=D0NUcHiskEnwSP99umP3zo8Fz8fl74OgAJ8NRDKCsp4=;
> > h=Date:From:Reply-To:To:In-Reply-To:References:Subject:List-Id:
> >  List-Unsubscribe;
> > b=R+WMLfhRZZdYxMd6K6w+iodDe8EHzwONNArNyboqsU5NnafPRhKZ1UeGxO/BCMvEK
> >  M7XHRRrBsPfRYpTph7xSGY427KGXieASVg1GDhAiwKSLBCiqDdkBaoJLLUIfUD02NS
> >  ouI3tvQ9mddNdaEK7retq8N+29hzs/ezf9cpgy+Q=
>
> Indeed the signature in "b=" was not made by the key at
> mail._domainkey.gitlab.haskell.org.  Running the below:
>
> sig=$(
> printf "%s\n%s\n%s\n" \
> R+WMLfhRZZdYxMd6K6w+iodDe8EHzwONNArNyboqsU5NnafPRhKZ1UeGxO/BCMvE \
> KM7XHRRrBsPfRYpTph7xSGY427KGXieASVg1GDhAiwKSLBCiqDdkBaoJLLUIfUD0 \
> 2NSouI3tvQ9mddNdaEK7retq8N+29hzs/ezf9cpgy+Q=
> )
>
> pkey=$(
> dig +short -t txt mail._domainkey.gitlab.haskell.org |
> perl -MMIME::Base64 -ne '
> /^"v=DKIM1;/ or next;
> print decode_base64($1) if m{;\s*p=(\S+?)(?:;|$)}
> ' |
> openssl pkey -pubin -inform DER
> )
>
> openssl rsautl -raw -encrypt -pubin \
> -inkey <( printf "%s\n" "$pkey" ) \
> -in <(printf "%s\n" "$sig" | openssl base64 -d) |
> xxd -p
>
> the output is:
>
> 509bfc93a492f1b5328308e51624d9a7ed1378861f577b11413c5034bc0c
> 673d61660434d4bc30844e7648da0f9605923805973a313a8c3bc82215cc
> ac447e47551087c544a0592ac3ae48474584bad7d9ca5b850a67493a7977
> d28aaa3a9a7580d165dc4f31ff484bdbc40e94a2be1750e71c51c555b5c1
> 6bc051947bb07ae4
>
> Which is not a PKCS#1.5 padded signature block.  So either the
> "b=" value was corrupted in transit, or it was signed by a key
> that is different from what is published in DNS.
>
> > but maybe Postfix  is not using the right key?
>
> Strictly speaking that's not Postfix itself, but some DKIM milter, but
> nits aside, more likely a stale public key is published in DNS.
>
> --
> Viktor.
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: DKIM failures for gitlab mail

[Viktor Dukhovni]

On Wed, Nov 30, 2022 at 05:33:44PM +0100, Joachim Breitner wrote:

> I noticed that a small number of Gitlab notification emails end up in
> my spamfilter. While there is not much you can do about triggering some
> bayesian style spam filter at my email provider (mailbox.org), I did
> notice this in the headers:
> 
> X-Spam-Status: No, score=2.704 tagged_above=2 required=6
> tests=[DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HS_RSPAMD_10_11=2.5,
> HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001,
> URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
> Authentication-Results: spamfilter01.heinlein-hosting.de (amavisd-new);
> dkim=fail (1024-bit key) reason="fail (bad RSA signature)"
> header.d=gitlab.haskell.org
> DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
> d=gitlab.haskell.org;
> s=mail; t=1669733134;
> bh=D0NUcHiskEnwSP99umP3zo8Fz8fl74OgAJ8NRDKCsp4=;
> h=Date:From:Reply-To:To:In-Reply-To:References:Subject:List-Id:
>  List-Unsubscribe;
> b=R+WMLfhRZZdYxMd6K6w+iodDe8EHzwONNArNyboqsU5NnafPRhKZ1UeGxO/BCMvEK
>  M7XHRRrBsPfRYpTph7xSGY427KGXieASVg1GDhAiwKSLBCiqDdkBaoJLLUIfUD02NS
>  ouI3tvQ9mddNdaEK7retq8N+29hzs/ezf9cpgy+Q=

Indeed the signature in "b=" was not made by the key at
mail._domainkey.gitlab.haskell.org.  Running the below:

sig=$(
printf "%s\n%s\n%s\n" \
R+WMLfhRZZdYxMd6K6w+iodDe8EHzwONNArNyboqsU5NnafPRhKZ1UeGxO/BCMvE \
KM7XHRRrBsPfRYpTph7xSGY427KGXieASVg1GDhAiwKSLBCiqDdkBaoJLLUIfUD0 \
2NSouI3tvQ9mddNdaEK7retq8N+29hzs/ezf9cpgy+Q=
)

pkey=$(
dig +short -t txt mail._domainkey.gitlab.haskell.org |
perl -MMIME::Base64 -ne '
/^"v=DKIM1;/ or next;
print decode_base64($1) if m{;\s*p=(\S+?)(?:;|$)}
' |
openssl pkey -pubin -inform DER
)

openssl rsautl -raw -encrypt -pubin \
-inkey <( printf "%s\n" "$pkey" ) \
-in <(printf "%s\n" "$sig" | openssl base64 -d) |
xxd -p

the output is:

509bfc93a492f1b5328308e51624d9a7ed1378861f577b11413c5034bc0c
673d61660434d4bc30844e7648da0f9605923805973a313a8c3bc82215cc
ac447e47551087c544a0592ac3ae48474584bad7d9ca5b850a67493a7977
d28aaa3a9a7580d165dc4f31ff484bdbc40e94a2be1750e71c51c555b5c1
6bc051947bb07ae4

Which is not a PKCS#1.5 padded signature block.  So either the
"b=" value was corrupted in transit, or it was signed by a key
that is different from what is published in DNS.

> but maybe Postfix  is not using the right key?

Strictly speaking that's not Postfix itself, but some DKIM milter, but
nits aside, more likely a stale public key is published in DNS.

-- 
Viktor.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

DKIM failures for gitlab mail

[Joachim Breitner]

Hi Bryan (I assume),

I noticed that a small number of Gitlab notification emails end up in
my spamfilter. While there is not much you can do about triggering some
bayesian style spam filter at my email provider (mailbox.org), I did
notice this in the headers:

X-Spam-Status: No, score=2.704 tagged_above=2 required=6
tests=[DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HS_RSPAMD_10_11=2.5,
HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001,
URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: spamfilter01.heinlein-hosting.de (amavisd-new);
dkim=fail (1024-bit key) reason="fail (bad RSA signature)"
header.d=gitlab.haskell.org
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
d=gitlab.haskell.org;
s=mail; t=1669733134;
bh=D0NUcHiskEnwSP99umP3zo8Fz8fl74OgAJ8NRDKCsp4=;
h=Date:From:Reply-To:To:In-Reply-To:References:Subject:List-Id:
 List-Unsubscribe;
b=R+WMLfhRZZdYxMd6K6w+iodDe8EHzwONNArNyboqsU5NnafPRhKZ1UeGxO/BCMvEK
 M7XHRRrBsPfRYpTph7xSGY427KGXieASVg1GDhAiwKSLBCiqDdkBaoJLLUIfUD02NS
 ouI3tvQ9mddNdaEK7retq8N+29hzs/ezf9cpgy+Q=


It seems the DKIM configuration is broken? There is a DKIM record for
the domain that’s valid acccording to 
https://www.dmarcanalyzer.com/de/dkim-de/dkim-record-check/?dmarcdns%5Btype%5D=dkim%5Bselector%5D=mail%5Bdomain%5D=gitlab.haskell.org=03AEkXODBDl43rk3Ww0q4J1LNooZNlqBYhWGd3spu68KM7nc3js92zXASAuHqVAek5IJj2iV26sx7LzrDQYX08fq2lnL5CvX4P4x7GOekNSV9yG9J48z0I3SxPzy5tQomgP4u9YR8yQqsmZwezj8coIagpBTce9Ubytv_nRg3oKmJjSYsJP5Pwc4Jmgn___e1nbsHUEqNWabdCJHX0Q02oZ3n3sRS5K8LpYOAFhYhOhMQF9QPQ74Uy8fc38lcuK3LJP6Dk5Z2xmgLJypXJiW4svbNTqnndkSehXM-Y5HJ7xdFZ3aMA4yiOwOOYjZwKc2reQDQ6v6TLrYnigFYgA6D4MM2PBRoc6-D5Zr3xbkjPMOlFVXNMGHpu_w4_nTIaTyRhYaBb1ilz7lYa15f8si5-vVuqT-XFe0U1nVsYHWBj-ejC3Ih7QQzaXdlegM3VMLZ94qBeK5b6uA7fbJv_EpMx3K6EbwVyfmsElNx9KnHOciAcQguIXUxU-EOTN900w-lAoqhxVG-VyqIQe8L99_eW6Ns5IV2tLp4qSg
but maybe Postfix  is not using the right key?

Cheers,
Joachim


-- 
Joachim Breitner
  m...@joachim-breitner.de
  http://www.joachim-breitner.de/

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab maintenance has started

[Bryan Richter via ghc-devs]

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 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, 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,
> > >>
> > >> 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, they will stay dead until the proper people can restart them.
> > >>
> > >> Sorry for the trouble!
> > >>
> > >> -Bryan
> > >>
> > >> On Thu, Nov 24, 2022 at 8:15 AM Bryan Richter  
> > >> wrote:
> > >> >
> > >> > Hi all,
> > >> >
> > >> > I've started the migration, so the maintenance period has officially 
> > >> > started.
> > >> >
> > >> > GitLab itself will go read-only soon.
> > >> >
> > >> > As a reminder, I scheduled 4 hours for the maintenance window.
> > >> >
> > >> > I'll send updates at major points of the migration.
> > >> >
> > >> > -Bryan
> > >> ___
> > >> ghc-devs mailing list
> > >> ghc-devs@haskell.org
> > >> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab maintenance has started

[Bryan Richter via ghc-devs]

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, 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,
> >>
> >> 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, they will stay dead until the proper people can restart them.
> >>
> >> Sorry for the trouble!
> >>
> >> -Bryan
> >>
> >> On Thu, Nov 24, 2022 at 8:15 AM Bryan Richter  
> >> wrote:
> >> >
> >> > Hi all,
> >> >
> >> > I've started the migration, so the maintenance period has officially 
> >> > started.
> >> >
> >> > GitLab itself will go read-only soon.
> >> >
> >> > As a reminder, I scheduled 4 hours for the maintenance window.
> >> >
> >> > I'll send updates at major points of the migration.
> >> >
> >> > -Bryan
> >> ___
> >> ghc-devs mailing list
> >> ghc-devs@haskell.org
> >> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab maintenance has started

[Bryan Richter via ghc-devs]

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,
>>
>> 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, they will stay dead until the proper people can restart them.
>>
>> Sorry for the trouble!
>>
>> -Bryan
>>
>> On Thu, Nov 24, 2022 at 8:15 AM Bryan Richter  
>> wrote:
>> >
>> > Hi all,
>> >
>> > I've started the migration, so the maintenance period has officially 
>> > started.
>> >
>> > GitLab itself will go read-only soon.
>> >
>> > As a reminder, I scheduled 4 hours for the maintenance window.
>> >
>> > I'll send updates at major points of the migration.
>> >
>> > -Bryan
>> ___
>> ghc-devs mailing list
>> ghc-devs@haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab maintenance has started

[Moritz Angermann]

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 maintenance
> mode. (That's not very helpful, but never mind.)
>
> As I do not have the access or privileges required to restart the
> runners, they will stay dead until the proper people can restart them.
>
> Sorry for the trouble!
>
> -Bryan
>
> On Thu, Nov 24, 2022 at 8:15 AM Bryan Richter 
> wrote:
> >
> > Hi all,
> >
> > I've started the migration, so the maintenance period has officially
> started.
> >
> > GitLab itself will go read-only soon.
> >
> > As a reminder, I scheduled 4 hours for the maintenance window.
> >
> > I'll send updates at major points of the migration.
> >
> > -Bryan
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab maintenance has started

[Bryan Richter via ghc-devs]

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, they will stay dead until the proper people can restart them.

Sorry for the trouble!

-Bryan

On Thu, Nov 24, 2022 at 8:15 AM Bryan Richter  wrote:
>
> Hi all,
>
> I've started the migration, so the maintenance period has officially started.
>
> GitLab itself will go read-only soon.
>
> As a reminder, I scheduled 4 hours for the maintenance window.
>
> I'll send updates at major points of the migration.
>
> -Bryan
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab maintenance has started

[Bryan Richter via ghc-devs]

Hi all,

I've started the migration, so the maintenance period has officially started.

GitLab itself will go read-only soon.

As a reminder, I scheduled 4 hours for the maintenance window.

I'll send updates at major points of the migration.

-Bryan
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab runners having issues

[Bryan Richter via ghc-devs]

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 not functioning right
> now, due to a problem with the ghc-perf-import bot. Until that gets
> resolved (later today, no doubt!), we'll see a higher pipeline failure
> rate.
>
> -Bryan
>
> On Tue, Nov 8, 2022 at 1:01 PM Bryan Richter  wrote:
> >
> > Hi everyone,
> >
> > Unfortunately, many CI jobs are failing for similar reasons on a
> > number of runners. Examples:
> >
> > 1.
> >
> > Running /usr/local/bin/cabal update --index=2020-12-21T14:48:20Z...
> > Downloading the latest package list from hackage.haskell.org
> > Version of /root.json is less than the previous version
> > /usr/local/bin/cabal update --index=2020-12-21T14:48:20Z failed
> > error: cabal update failed
> >
> > -- https://gitlab.haskell.org/ghc/ghc/-/jobs/1224391
> >
> >
> > 2.
> >
> > ERROR: Job failed: failed to pull image
> > "registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-v15.0.0"
> >
> > -- https://gitlab.haskell.org/ghc/ghc/-/jobs/1224641
> >
> > Moritz, can you look into these?
> >
> > Could it have something to do with the GitLab emergency upgrade that
> > happened yesterday? Or were the runners reconfigured in some way?
> >
> > I don't have administrative access to these runners.
> >
> > I have created an issue: https://gitlab.haskell.org/ghc/ghc/-/issues/22422
> >
> > -Bryan
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab slow?

[Simon Peyton Jones]

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 bandwidth.
> > We rely on Ben still. (I am at least relieving him of other tasks that
> > would be competing for his time!)
> >
> Hmm, interesting. I'm not seeing anything particularly concerning with
> the load times. According to Firefox's network profiler
> https://gitlab.haskell.org/ghc/ghc/-/issues/22451 takes about 3 seconds
> to load, with the DOM being loaded with 500ms. While this isn't fast per
> se, it's about in line with what I would expect.
>
> Are either of you seeing significantly longer load times?
>
> Cheers,
>
> - Ben
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab slow?

[Hécate]

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, Ben Gamari a écrit :

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 competing for his time!)


Hmm, interesting. I'm not seeing anything particularly concerning with
the load times. According to Firefox's network profiler
https://gitlab.haskell.org/ghc/ghc/-/issues/22451 takes about 3 seconds
to load, with the DOM being loaded with 500ms. While this isn't fast per
se, it's about in line with what I would expect.

Are either of you seeing significantly longer load times?

Cheers,

- Ben

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs


--
Hécate ✨
: @TechnoEmpress
IRC: Hecate
WWW: https://glitchbra.in
RUN: BSD

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab slow?

[Ben Gamari]

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 competing for his time!)
>
Hmm, interesting. I'm not seeing anything particularly concerning with
the load times. According to Firefox's network profiler
https://gitlab.haskell.org/ghc/ghc/-/issues/22451 takes about 3 seconds
to load, with the DOM being loaded with 500ms. While this isn't fast per
se, it's about in line with what I would expect.

Are either of you seeing significantly longer load times?

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab slow?

[Bryan Richter via ghc-devs]

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 1:03 PM Simon Peyton Jones
 wrote:
>
> Is it just me, or is GitLab taking an unusually long time to serve up pages 
> when looking at GHC tickets?
>
> Simon
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Gitlab slow?

[Simon Peyton Jones]

Is it just me, or is GitLab taking an unusually long time to serve up pages
when looking at GHC tickets?

Simon
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab runners having issues

[Hécate]

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
now, due to a problem with the ghc-perf-import bot. Until that gets
resolved (later today, no doubt!), we'll see a higher pipeline failure
rate.

-Bryan

On Tue, Nov 8, 2022 at 1:01 PM Bryan Richter  wrote:

Hi everyone,

Unfortunately, many CI jobs are failing for similar reasons on a
number of runners. Examples:

1.

Running /usr/local/bin/cabal update --index=2020-12-21T14:48:20Z...
Downloading the latest package list from hackage.haskell.org
Version of /root.json is less than the previous version
/usr/local/bin/cabal update --index=2020-12-21T14:48:20Z failed
error: cabal update failed

-- https://gitlab.haskell.org/ghc/ghc/-/jobs/1224391


2.

ERROR: Job failed: failed to pull image
"registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-v15.0.0"

-- https://gitlab.haskell.org/ghc/ghc/-/jobs/1224641

Moritz, can you look into these?

Could it have something to do with the GitLab emergency upgrade that
happened yesterday? Or were the runners reconfigured in some way?

I don't have administrative access to these runners.

I have created an issue: https://gitlab.haskell.org/ghc/ghc/-/issues/22422

-Bryan

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs


--
Hécate ✨
: @TechnoEmpress
IRC: Hecate
WWW: https://glitchbra.in
RUN: BSD

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab runners having issues

[Bryan Richter via ghc-devs]

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 doubt!), we'll see a higher pipeline failure
rate.

-Bryan

On Tue, Nov 8, 2022 at 1:01 PM Bryan Richter  wrote:
>
> Hi everyone,
>
> Unfortunately, many CI jobs are failing for similar reasons on a
> number of runners. Examples:
>
> 1.
>
> Running /usr/local/bin/cabal update --index=2020-12-21T14:48:20Z...
> Downloading the latest package list from hackage.haskell.org
> Version of /root.json is less than the previous version
> /usr/local/bin/cabal update --index=2020-12-21T14:48:20Z failed
> error: cabal update failed
>
> -- https://gitlab.haskell.org/ghc/ghc/-/jobs/1224391
>
>
> 2.
>
> ERROR: Job failed: failed to pull image
> "registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-v15.0.0"
>
> -- https://gitlab.haskell.org/ghc/ghc/-/jobs/1224641
>
> Moritz, can you look into these?
>
> Could it have something to do with the GitLab emergency upgrade that
> happened yesterday? Or were the runners reconfigured in some way?
>
> I don't have administrative access to these runners.
>
> I have created an issue: https://gitlab.haskell.org/ghc/ghc/-/issues/22422
>
> -Bryan
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab runners having issues

[Bryan Richter via ghc-devs]

Hi everyone,

Unfortunately, many CI jobs are failing for similar reasons on a
number of runners. Examples:

1.

Running /usr/local/bin/cabal update --index=2020-12-21T14:48:20Z...
Downloading the latest package list from hackage.haskell.org
Version of /root.json is less than the previous version
/usr/local/bin/cabal update --index=2020-12-21T14:48:20Z failed
error: cabal update failed

-- https://gitlab.haskell.org/ghc/ghc/-/jobs/1224391


2.

ERROR: Job failed: failed to pull image
"registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-v15.0.0"

-- https://gitlab.haskell.org/ghc/ghc/-/jobs/1224641

Moritz, can you look into these?

Could it have something to do with the GitLab emergency upgrade that
happened yesterday? Or were the runners reconfigured in some way?

I don't have administrative access to these runners.

I have created an issue: https://gitlab.haskell.org/ghc/ghc/-/issues/22422

-Bryan
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab maintenance today

[Ben Gamari]

Hi all,

Today we will be doing some maintenance on gitlab.haskell.org to address
#22418. I can't yet say precisely when the outage will begin but I do
expect there to be one. I will try to provide at least 30 minutes
notice.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GItlab search

[Ben Gamari]

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 dear, indeed. The problem is that GitLab paused indexing due to a
version incompatibility. I have fixed the issue and unpaused the
indexer.

Searching for '"-DDEBUG" slow' now turns up #22200 as the first result.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GItlab search

[Simon Peyton Jones]

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.

Looking for DEBUG or *DEBUG also fails. I find that DDEBUG succeeds.  What
are the rules?

Thanks

Simon
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab labels

[Douglas Wilson]

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.haskell.org/help/user/project/quick_actions

Regards,
Douglas Wilson

On 7/28/22, Bryan Richter via ghc-devs  wrote:
> 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 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, Simon Peyton Jones wrote:
>>> Whenever I try to add a label to a ticket I get "an error occurred while
>>> updating labels".  See below.
>>>
>>> When I repeat the exact same sequence, it works.
>>>
>>> If I add another label, again the error; repeating again works.
>>>
>>> This is tiresome and peculiar.  Does anyone have any ideas?
>>>
>>> Simon
>>>
>>> [image: image.png]
>>
>>
>>
>>> ___
>>> ghc-devs mailing list
>>> ghc-devs@haskell.org
>>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>>
>> ___
>> ghc-devs mailing list
>> ghc-devs@haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab labels

[Bryan Richter via ghc-devs]

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 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, Simon Peyton Jones wrote:

Whenever I try to add a label to a ticket I get "an error occurred while
updating labels".  See below.

When I repeat the exact same sequence, it works.

If I add another label, again the error; repeating again works.

This is tiresome and peculiar.  Does anyone have any ideas?

Simon

[image: image.png]





___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs


___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab labels

[Zubin Duggal]

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, Simon Peyton Jones wrote:

Whenever I try to add a label to a ticket I get "an error occurred while
updating labels".  See below.

When I repeat the exact same sequence, it works.

If I add another label, again the error; repeating again works.

This is tiresome and peculiar.  Does anyone have any ideas?

Simon

[image: image.png]





___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs


___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Gitlab labels

[Simon Peyton Jones]

Whenever I try to add a label to a ticket I get "an error occurred while
updating labels".  See below.

When I repeat the exact same sequence, it works.

If I add another label, again the error; repeating again works.

This is tiresome and peculiar.  Does anyone have any ideas?

Simon

[image: image.png]
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab bullets

[Simon Peyton Jones]

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 all have a newline
> after
> >them
> >- Ditto the numbered points under "Generalisation"
> >- But some bullets under "Generalisation" are OK.
> >- Bullets have a handle that seems to let you drag the bullet around.
> >But if you do so, it messa up the format  completely!
> >
> > Ben, can you revert this Gitlab change?
> >
> Indeed I also noticed this. I sneakily updated to 15.0.2 this morning,
> which indeed seems to have fixed the regression.
>
> Do let me know if anything else looks amiss.
>
> Cheers,
>
> - Ben
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab bullets

[Ben Gamari]

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"
>- But some bullets under "Generalisation" are OK.
>- Bullets have a handle that seems to let you drag the bullet around.
>But if you do so, it messa up the format  completely!
>
> Ben, can you revert this Gitlab change?
>
Indeed I also noticed this. I sneakily updated to 15.0.2 this morning,
which indeed seems to have fixed the regression.

Do let me know if anything else looks amiss.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab bullets

[Giorgio Marinelli]

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 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"
> But some bullets under "Generalisation" are OK.
> Bullets have a handle that seems to let you drag the bullet around.  But if 
> you do so, it messa up the format  completely!
>
> Ben, can you revert this Gitlab change?
>
> Simon
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab bullets

[Simon Peyton Jones]

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"
   - But some bullets under "Generalisation" are OK.
   - Bullets have a handle that seems to let you drag the bullet around.
   But if you do so, it messa up the format  completely!

Ben, can you revert this Gitlab change?

Simon
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab upgrade starting shortly

[Ben Gamari]

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/ghc-devs

Re: GitLab upgrade starting shortly

[Ben Gamari]

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
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab upgrade starting shortly

[Ben Gamari]

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 7, 2022 10:54:31 PM EDT, Ben Gamari  wrote:
>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 be two
>> more periods of brief downtime as we migrate to 4.10 and then 5.0. I
>> will write to the list when the next down period begins.
>>
>The second phase of the migration will begin shortly.
>
>
>Cheers,
>
> - Ben
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab upgrade starting shortly

[Ben Gamari]

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 be two
> more periods of brief downtime as we migrate to 4.10 and then 5.0. I
> will write to the list when the next down period begins.
>
The second phase of the migration will begin shortly.


Cheers,

 - Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab upgrade starting shortly

[Ben Gamari]

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 downtime as we migrate to 4.10 and then 5.0. I
will write to the list when the next down period begins.

Cheers,

- Ben



signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab upgrade starting shortly

[Ben Gamari]

Hello all,

I will be starting the GitLab upgrade shortly. Expect approximately 30
minutes of downtime.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab upgrade tonight

[Ben Gamari]

Hello everyone,

Tonight, around 20:00 EST, I will be performing a GitLab upgrade. As
always, the downtime should be minimal (less than 30 minutes) but I will
provide status updates as necessary.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab spam

[Ben Gamari]

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 to this; it is a security
> concern.
>
I have never seen a spam user attempt to use our CI infrastructure.
While I believe we could in principle disable CI for new users now since
this feature request has (AFAICT) been implemented [1], I am a bit
reluctant to do so unless there is actual evidence of abuse.

Cheers,

- Ben


[1] https://gitlab.com/groups/gitlab-org/-/epics/3278


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab spam

[Moritz Angermann]

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.

Moritz

On Tue, 17 May 2022 at 1:27 AM, Ben Gamari  wrote:

> 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
> we shouldn't worry lose any sleep over it. On the other hand, spam
> content is quite problematic and we should strive to eliminate it.
> Once every few months I take a bit of time and do some cleaning (with
> some mechanical help [1]). It's also helpful when users use GitLab's
> "Report Abuse" feature to flag spam accounts as these cases are very
> easy to handle.
>
> Cheers,
>
> - Ben
>
>
> [1]
> https://gitlab.haskell.org/bgamari/ghc-utils/-/blob/master/gitlab-utils/gitlab_utils/spam_util.py
>
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab spam

[Ben Gamari]

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
we shouldn't worry lose any sleep over it. On the other hand, spam
content is quite problematic and we should strive to eliminate it.
Once every few months I take a bit of time and do some cleaning (with
some mechanical help [1]). It's also helpful when users use GitLab's
"Report Abuse" feature to flag spam accounts as these cases are very
easy to handle.

Cheers,

- Ben


[1] 
https://gitlab.haskell.org/bgamari/ghc-utils/-/blob/master/gitlab-utils/gitlab_utils/spam_util.py



signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab spam

[Hécate]

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 anyone) is the moderation team that handles abuse reports?

While I don't think it's a high-priority concern for myself and I 
don't intend to address it right now, I'd like to at least know what 
kind of effect this is having on GHC devs.


There have already been 50+ users added today, and a random sample was 
100% spam.


There are 84,000 users and 1700 projects in the system in total. I 
assume 90-99% of them are spam. Not really conducive to a balanced diet.


-Bryan "eat more veggies" Richter

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs


--
Hécate ✨
: @TechnoEmpress
IRC: Hecate
WWW:https://glitchbra.in
RUN: BSD
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

gitlab spam

[Bryan]

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 anyone) is the moderation team that handles abuse reports?

While I don't think it's a high-priority concern for myself and I don't intend 
to address it right now, I'd like to at least know what kind of effect this is 
having on GHC devs.

There have already been 50+ users added today, and a random sample was 100% 
spam.

There are 84,000 users and 1700 projects in the system in total. I assume 
90-99% of them are spam. Not really conducive to a balanced diet.

-Bryan "eat more veggies" Richter___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab problem

[Simon Peyton Jones]

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:
> >
> > 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 allocation request failed on channel 0
> > Welcome to GitLab, @simonpj!
> > Connection to gitlab.haskell.org closed.
> >
> > How could I debug this?  I'm on WSL.  My network appears to be fine.
> >
> > Thanks.  I'm totally stalled.
> >
> > Simon
> > ___
> > ghc-devs mailing list
> > ghc-devs@haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab problem

[Matthew Pickering]

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 allocation request failed on channel 0
> Welcome to GitLab, @simonpj!
> Connection to gitlab.haskell.org closed.
>
> How could I debug this?  I'm on WSL.  My network appears to be fine.
>
> Thanks.  I'm totally stalled.
>
> Simon
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Gitlab problem

[Simon Peyton Jones]

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 allocation request failed on channel 0
Welcome to GitLab, @simonpj!
Connection to gitlab.haskell.org closed.

How could I debug this?  I'm on WSL.  My network appears to be fine.

Thanks.  I'm totally stalled.

Simon
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: how to complete a review on gitlab?

[Richard Eisenberg]

I think you just unassign yourself using the widget on the right: Click on the 
reviewers button, and you should see yourself highlighted. Click your own icon, 
and that should remove you from the ticket.

Richard

> On Feb 9, 2022, at 10:35 AM, Norman Ramsey  wrote:
> 
> I've been assigned a few merge requests to review on gitlab.  One I've
> completed and approved.  One I've completed and have decided that
> somebody else needs to approve it; I'm not qualified.  Two I've not
> yet started.
> 
> Is there any way to tell gitlab, "I'm done with these two"?
> 
> 
> Norman
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

how to complete a review on gitlab?

[Norman Ramsey]

I've been assigned a few merge requests to review on gitlab.  One I've
completed and approved.  One I've completed and have decided that
somebody else needs to approve it; I'm not qualified.  Two I've not
yet started.

Is there any way to tell gitlab, "I'm done with these two"?


Norman
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: meaning of title of merge request on gitlab?

[Sam Derbyshire]

As far as I understand, WIP and Draft are equivalent.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

meaning of title of merge request on gitlab?

[Norman Ramsey]

I've opened a very, very preliminary MR.  The Commentary instructs me
to tag it "WIP: ", but gitlab seems to suggest that in order to 
prevent it from being merged, I need "Draft: ".  When a merge
request is both WIP and Draft, how should it be titled?

(The MR in question is https://gitlab.haskell.org/ghc/ghc/-/merge_requests/7442)


Norman
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: [PSA] Patches to Haddock regarding GHC development move to GitLab!

[Richard Eisenberg]

Hi Hécate,

Thanks for this announcement.

Can you also update the documentation in 
https://gitlab.haskell.org/ghc/ghc/-/wikis/repositories to reflect this change? 
That wiki page remains my go-to source for this kind of information.

That page also says that 
https://gitlab.haskell.org/ghc/ghc/-/blob/master/packages is the authoritative 
place to look for submodule information. Does that need updating, too?

Thanks! :)
Richard

> On Dec 17, 2021, at 11:47 AM, Hécate  wrote:
> 
> Hi everyone, just a PSA from the Haddock team and GHC release managers to 
> warn everyone that, effective immediately, patches to Haddock needed for GHC 
> merge requests are not to be directed to GitHub anymore.
> 
> Those patches are to be sent to the GitLab mirror: 
> https://gitlab.haskell.org/ghc/haddock.
> 
> I will try and warn folks who currently have PRs opened on GitHub targeting 
> ghc-head, but please know that they'll be closed in the next few days.
> 
> Have a great end of the week,
> Hécate, for the Haddock Team.
> 
> -- 
> Hécate ✨
> : @TechnoEmpress
> IRC: Hecate
> WWW: https://glitchbra.in
> RUN: BSD
> 
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

[PSA] Patches to Haddock regarding GHC development move to GitLab!

[Hécate]

Hi everyone, just a PSA from the Haddock team and GHC release managers 
to warn everyone that, effective immediately, patches to Haddock needed 
for GHC merge requests are not to be directed to GitHub anymore.


Those patches are to be sent to the GitLab mirror: 
https://gitlab.haskell.org/ghc/haddock.


I will try and warn folks who currently have PRs opened on GitHub 
targeting ghc-head, but please know that they'll be closed in the next 
few days.


Have a great end of the week,
Hécate, for the Haddock Team.

--
Hécate ✨
: @TechnoEmpress
IRC: Hecate
WWW: https://glitchbra.in
RUN: BSD

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab upgrade starting soon

[Ben Gamari]

Hi all,

I will be performing an upgrade of gitlab.haskell.org in roughly 30
minutes if there are no objections. I expect the down-time to be on the
order of 20 minutes.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab likes Chrome more than Firefox

[Norman Ramsey]

 > 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" part of a Github PR, and I assume it will have similar
issues with Gitlab.


Norman
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab likes Chrome more than Firefox

[Richard Eisenberg]

Hi all,

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. I will be 
routinely using Chrome to review large patches from now on. You may want to, 
too.

Richard
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

RE: Gitlab

[Ben Gamari]

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.

Apoloegies for the inconvenience!

Cheers,

- Ben



signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

RE: Gitlab

[Simon Peyton Jones via ghc-devs]

It started working again, a few mins after it stopped working. I was getting 
consistent Error 500, then started being OK.  

Strange.

Simon

PS: I am leaving Microsoft at the end of November 2021, at which point 
simo...@microsoft.com will cease to work.  Use simon.peytonjo...@gmail.com 
instead.  (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 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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitl
|  ab.haskell.org%2Fghc%2Fhaddockdata=04%7C01%7Csimonpj%40microsoft.
|  com%7Ca9e47aca8f374f19f98008d994723bf3%7C72f988bf86f141af91ab2d7cd011d
|  b47%7C1%7C0%7C637704041244004412%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wL
|  jAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000sdata
|  =QF5AEHaNFKWepD697Jvtz1pr70%2B4GaK4RuKTBSaFgLI%3Dreserved=0 (in
|  Firefox)
|  
|  * git clone
|  https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitl
|  ab.haskell.org%2Fghc%2Fhaddock.gitdata=04%7C01%7Csimonpj%40micros
|  oft.com%7Ca9e47aca8f374f19f98008d994723bf3%7C72f988bf86f141af91ab2d7cd
|  011db47%7C1%7C0%7C637704041244004412%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiM
|  C4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000s
|  data=zPu4532C%2FsdgdIyZu2ExDvFHBTNtsd7IQfMhsmV47EM%3Dreserved=0
|  /tmp/haddock
|  
|  * git clone g...@gitlab.haskell.org:ghc/haddock.git /tmp/haddock-2
|  
|  Simon, can you give more precise details about the problem you are
|  experiencing?
|  
|  Tom
|  ___
|  ghc-devs mailing list
|  ghc-devs@haskell.org
|  https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.
|  haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-
|  devsdata=04%7C01%7Csimonpj%40microsoft.com%7Ca9e47aca8f374f19f980
|  08d994723bf3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637704041244
|  004412%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJ
|  BTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000sdata=CC%2F0tJSLYXL8A763MtT9%2F
|  Y%2BQG7PL3cSngakqUcFUDes%3Dreserved=0
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab

[Sam Derbyshire]

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

[Tom Ellis]

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://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab

[Sam Derbyshire]

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

[Tom Ellis]

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://gitlab.haskell.org/ghc/haddock.git /tmp/haddock 

* git clone g...@gitlab.haskell.org:ghc/haddock.git /tmp/haddock-2

Simon, can you give more precise details about the problem you are
experiencing?

Tom
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab

[Matthew Pickering]

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 work.  Use simon.peytonjo...@gmail.com 
> instead.  (For now, it just forwards to simo...@microsoft.com.)
>
>
>
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Gitlab

[Sam Derbyshire]

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

Gitlab

[Simon Peyton Jones via ghc-devs]

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<mailto:simo...@microsoft.com> will cease to work.  Use 
simon.peytonjo...@gmail.com<mailto:simon.peytonjo...@gmail.com> instead.  (For 
now, it just forwards to simo...@microsoft.com.)

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab outage

[Ben Gamari]

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 develops.
>
> I see that gitlab is back up, but also that its host key has changed.
> That would make sense if you have migrated to an existing machine with
> its own configuration.  But could you kindly please confirm that
> fingerprint for the new host is expected to be as follows?
>
Indeed I realized the mistake shortly after sending my previous email
and restored the host key.

The host keys are:

gitlab.haskell.org ssh-ed25519 
C3NzaC1lZDI1NTE5IA7ltOZyaULDgxE3Vw6RgQVp+OPKQi79ssUenbhdWy36
gitlab.haskell.org ssh-rsa 
B3NzaC1yc2EDAQABAAACAQDSzzl8mwY6ohtW6MftKaQfta8yTL8cTxtA7lcueo2mkPpwBBQ7FA6z3nFATx25QwdV7fa7DuNRDX57f/a/W7+wMhXZ6yyQr+gwr0h4vdZ8Nt4XNfNdkdGw4fZKRApWxyvfSkxjs/E9+G0o3eQLspxjVohBkmkcsowpFUI5Aazv/K6QIf1gKt+4iPvYcB/dBJ1yF1qmpayz4htrKyUC5l3GCBEwvMdAjIQ2bX8pyjTtqcJDLosAVzQ5wprkdgkL29MgJXEbM+B1d1log0hnX4AsbOlL7tWhTO1Je2hSuEeiVaDDPFUyCoGQRFDrisQU5lb8NrzuN3jpNc+PxOHbXHfaTppAoED/++UepvgtLF1zUM13cRk56YmpmABOa48W72VJuzLLm8DF+KBWBs6TDuVk3y9z/SS6zDS0VGkHotldopW2kpsjErJIdWVKIL3RP/Flay7mzl3l/izIMTHXXKMxV3/+XaBjG/gDOCld3JjORQXah2hvJfvXeNaePE1RKAMS63cj3XTE77fsYH7VmEdE34RTBDtsZR5WhEjdf29hjEcQDPf0vDphxRHr6IqUSwVcd7ps6nVoccTfaepJm62IIXDgOsc2piWl2xXNZJVtph6U+MzsPDSSbu1MTwalwgqpApcYK7ZzUjGHA7+NBhjjSuUZO6eHzwxjAn0FXZyrpQ==

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab outage

[Ben Gamari]

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 develops.
>
Hello all,

I have finished bringing up GitLab on a new instance which I'm hoping
should have enough storage for many years to come. Apologies for the
down-time and thanks for your patience.

Cheers,

- Ben



signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab outage

[Norman Ramsey]

 > 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 back up, but also that its host key has changed.
That would make sense if you have migrated to an existing machine with
its own configuration.  But could you kindly please confirm that
fingerprint for the new host is expected to be as follows?

The fingerprint for the ED25519 key sent by the remote host is
SHA256:pPSesloVW0X6zUe/fJ+ZSK8NttS0WiDlFt/VDS06Ugs.


Norman
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab outage

[Ben Gamari]

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 develops.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab summary note on review

[Ben Gamari]

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, you can write a comment at the bottom, and,
> critically, add it to the review. Then, when you submit the review,
> the summary comment goes with it.
>
For what it's worth, this is a somewhat new feature that was added, at
least in part, in response to our feedback. We owe some thanks to our
friends at GitLab for their responsiveness.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

GitLab summary note on review

[Richard Eisenberg]

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, you can write a comment at the bottom, and, critically, 
add it to the review. Then, when you submit the review, the summary comment 
goes with it.

Happy reviewing,
Richard
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab downtime

[Ben Gamari]

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 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 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 critical should be functional.
>Do let me
>> >> > know if you find anything amiss.
>> >> >
>> >> > Cheers,
>> >> >
>> >> > - Ben
>> >> > ___
>> >> > ghc-devs mailing list
>> >> > ghc-devs@haskell.org
>> >> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>> >>
>> >> ___
>> >> ghc-devs mailing list
>> >> ghc-devs@haskell.org
>> >> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>> >
>> >
>> >
>> > --
>> > Shayne Fletcher
>> > ___
>> > ghc-devs mailing list
>> > ghc-devs@haskell.org
>> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>> ___
>> ghc-devs mailing list
>> ghc-devs@haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>___
>ghc-devs mailing list
>ghc-devs@haskell.org
>http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab downtime

[Giorgio Marinelli]

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 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 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,
> >> >
> >> > - Ben
> >> > ___
> >> > ghc-devs mailing list
> >> > ghc-devs@haskell.org
> >> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
> >>
> >> ___
> >> ghc-devs mailing list
> >> ghc-devs@haskell.org
> >> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
> >
> >
> >
> > --
> > Shayne Fletcher
> > ___
> > ghc-devs mailing list
> > ghc-devs@haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab downtime

[Matthew Pickering]

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 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 critical should be functional. Do let me
>> > know if you find anything amiss.
>> >
>> > Cheers,
>> >
>> > - Ben
>> > ___
>> > ghc-devs mailing list
>> > ghc-devs@haskell.org
>> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>>
>> ___
>> ghc-devs mailing list
>> ghc-devs@haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
>
>
> --
> Shayne Fletcher
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab downtime

[Shayne Fletcher]

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 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,
> >
> > - Ben
> > ___
> > ghc-devs mailing list
> > ghc-devs@haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>


-- 
Shayne Fletcher
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: GitLab downtime

[Vladislav Zavialov]

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 critical should be functional. Do let me
> know if you find anything amiss.
> 
> Cheers,
> 
> - Ben
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs