Re: GitLab downtime

2021-06-01 Thread 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

2021-06-01 Thread 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: Give MonadTrans a QuantifiedConstraints superclass

2021-06-01 Thread chessai 
I think you meant to forward to the libraries mailing list, not the
ghc-devs one

On Tue, Jun 1, 2021, 18:01 Baldur Blöndal  wrote:

> This is to advertise the proposal
> (https://gitlab.haskell.org/ghc/ghc/-/issues/19922) to add a
> superclass to the MonadTrans type class in Control.Monad.Trans.
>
> A Monad transformer 'trans' lifts a 'Monad m' to a 'Monad (trans m)'.
>
> This proposal code-ifies that with a superclass constraint, an
> impliciation constraint enabled by the recent extension
> QuantifiedConstraints:
>
> class (forall m. Monad m => Monad (trans m)) => MonadTrans trans where
>   ..
>
> This is the main motiviating example of the Quantified Class
> Constraints paper https://gkaracha.github.io/papers/quantcs.pdf
> ___
> 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

Give MonadTrans a QuantifiedConstraints superclass

2021-06-01 Thread Baldur Blöndal 
This is to advertise the proposal
(https://gitlab.haskell.org/ghc/ghc/-/issues/19922) to add a
superclass to the MonadTrans type class in Control.Monad.Trans.

A Monad transformer 'trans' lifts a 'Monad m' to a 'Monad (trans m)'.

This proposal code-ifies that with a superclass constraint, an
impliciation constraint enabled by the recent extension
QuantifiedConstraints:

class (forall m. Monad m => Monad (trans m)) => MonadTrans trans where
  ..

This is the main motiviating example of the Quantified Class
Constraints paper https://gkaracha.github.io/papers/quantcs.pdf
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: value of documenting error messages?

2021-06-01 Thread Alec Theriault 
Hello,

If these are the messages that get pretty-printed into errors or warnings,
I would think detailed documentation is definitely useful. However, since
this is documentation that users of GHC will want to read (and not just
contributors), I think it should live primarily in the user's guide and not
the Haddocks.

Rust has taken an interesting approach for this: every error message is
given a unique number like "E0119" and there is an error index
 generated from simple
markdown files

containing explanations and examples for the errors (error codes by
themselves already massively help searchability). If GHC were to take this
approach, I think it would be fine to just include the error message
identifier in the Haddocks.

Alec

PS: Rust even bundles the documentation for errors into the compiler, so
you can do something like `rustc --explain E0119` to get the full
description of the error. It'd be pretty neat if GHC could do this too.
Some errors don't have much to say about them, but others definitely could
be explained!

On Tue, Jun 1, 2021 at 2:36 PM Richard Eisenberg  wrote:

> Hi devs,
>
> Take a quick look at
> https://gitlab.haskell.org/ghc/ghc/-/blob/6db8a0f76ec45d47060e28bb303e9eef60bdb16b/compiler/GHC/Driver/Errors/Types.hs#L107
> You will see a datatype there with constructors describing error messages
> that GHC might produce. These constructors have comments describing the
> error, sometimes giving an example, and sometimes listing test cases. More
> datatypes like this one and more constructors in these datatypes are on the
> way.
>
> Question: Is there sufficient value in carefully documenting each
> constructor?
>
> In my ideal world, each constructor would have a high-level description, a
> detailed description of each field, an example of a program that generates
> the error, and one or more test cases that test the output. Along the way,
> we might discover that no such test case exists, and then we would add.
> However, generating this documentation is hard. I was thinking of whipping
> up an army of volunteers (Hécate has advised me how to do this) to do the
> work, but that army will need to be fed (with instructions, supervision,
> and reviews) and will want to know that their work is important. Is this
> effort worthwhile? Do we see ourselves maintaining this documentation? Or
> is the effort better spent elsewhere, perhaps tagging each constructor with
> an ID and then making wiki pages? Not sure what's best -- would love ideas!
>
> Credit to Alfredo di Napoli, who's done the heavy lifting of getting us
> this far.
>
> Relevant tickets:
> Original: https://gitlab.haskell.org/ghc/ghc/-/issues/18516
> Tasks left: https://gitlab.haskell.org/ghc/ghc/-/issues/19905
>
> Thanks,
> Richard
> ___
> 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

value of documenting error messages?

2021-06-01 Thread Richard Eisenberg 
Hi devs,

Take a quick look at 
https://gitlab.haskell.org/ghc/ghc/-/blob/6db8a0f76ec45d47060e28bb303e9eef60bdb16b/compiler/GHC/Driver/Errors/Types.hs#L107
 

  You will see a datatype there with constructors describing error messages 
that GHC might produce. These constructors have comments describing the error, 
sometimes giving an example, and sometimes listing test cases. More datatypes 
like this one and more constructors in these datatypes are on the way.

Question: Is there sufficient value in carefully documenting each constructor?

In my ideal world, each constructor would have a high-level description, a 
detailed description of each field, an example of a program that generates the 
error, and one or more test cases that test the output. Along the way, we might 
discover that no such test case exists, and then we would add. However, 
generating this documentation is hard. I was thinking of whipping up an army of 
volunteers (Hécate has advised me how to do this) to do the work, but that army 
will need to be fed (with instructions, supervision, and reviews) and will want 
to know that their work is important. Is this effort worthwhile? Do we see 
ourselves maintaining this documentation? Or is the effort better spent 
elsewhere, perhaps tagging each constructor with an ID and then making wiki 
pages? Not sure what's best -- would love ideas!

Credit to Alfredo di Napoli, who's done the heavy lifting of getting us this 
far.

Relevant tickets: 
Original: https://gitlab.haskell.org/ghc/ghc/-/issues/18516
Tasks left: https://gitlab.haskell.org/ghc/ghc/-/issues/19905

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

Re: GitLab downtime

2021-06-01 Thread 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

2021-06-01 Thread 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

2021-06-01 Thread 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