- ghc-devs - Haskell.org

Release Status - 9.4.1-alpha2/9.2.3/9.0.* series
by Matthew Pickering 24 May '22

24 May '22

Hi all, I will shortly prepare a blog post which describes the situation in more detail for a general audience but for the subscribers here is a summary of the release status. 9.4.1-alpha2: The release is imminent, and fixes a number of packaging issues identified with alpha1. Slightly delayed due to regression involving deb9 toolchains. (Ben) 9.2.3: The release will follow shortly (within 1 week) after the 9.4.1-alpha2 release. Slightly delayed due to 9.4.1-alpha2 delay. (Zubin) 9.4.1: The target for the final release is end of July. 9.0.* series: We do not intend to do any more releases in the 9.0.* series. - The 9.2 series is more stable - The 9.2 series does not contain significant breakage (when upgrading from 9.0) - Anecdotal evidence suggests users are upgrading straight from 8.10.7 to 9.2.2 - We do not have capacity to manage 4 active branches. Any thoughts, please reply promptly before I communicate these facts with the community. Best Wishes, Matt

3 3

best way to detect invalid Haddock early?
by Norman Ramsey 23 May '22

23 May '22

I've had some CI failures because of invalid Haddock comments. What is the best way to detect such issues locally, early? I tried setting environment variable GHC_FLAGS to "-Winvalid-haddock", which should have told `./hadrian/ghci` to issue a warning. But for some reason, no warning was issued. What's a good way to detect invalid Haddock before it hits CI? Norman

1 0

gitlab spam
by Bryan 17 May '22

17 May '22

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

4 4

ambiguous record field (but not *that* kind of ambiguous record field)
by Richard Eisenberg 16 May '22

16 May '22

Hi all, On a project I'm working on, I wish to declare something like data Rec = MkRec { field :: forall a. SomeConstraint a => ... } where the ... contains no mention of `a`. Even with https://github.com/ghc-proposals/ghc-proposals/pull/448 <https://github.com/ghc-proposals/ghc-proposals/pull/448>, I think there is no way to avoid the ambiguity when setting `field`. Is that correct? If so, what shall we do about it? The natural answer is somehow to write ... MkRec { field @a = ... } ... but that would break significant new syntactic ground. (Maybe it's good new syntactic ground, but it would still be very new.) Thanks, Richard

3 3

Welcome to Bryan (Devops Engineer)
by Matthew Pickering 16 May '22

16 May '22

Hi all, Bryan has been hired by the Haskell foundation to work on devops problems in the Haskell ecosystem. His first day is today! At least initially he will be working closely with the GHC team to shore up CI infrastructure and other devops tasks. If you see him around make sure to say hello, especially if you've got a complaint about CI ;) His username is chreekat. Cheers, Matt

3 2

Deprecation of GHCi's tag generation feature, starting with GHC 9.4
by Hécate 15 May '22

15 May '22

Hello devs, Last year was discussed the deprecation of GHCi's tag generation feature, as it had become a liability with recent additions to the language, like Unboxed Sums¹. The deprecation process starts with GHC 9.4, and merge request !6325². TL;DR: The ghc-tags tool has been elected to replace the tags feature. This is being documented in the "Tags" wiki page³. You are invited to help with broadcasting this announcement to your fellow Haskell users. I will post on Reddit and the Haskell Discourse but increasing the coverage of this will be important. Cheers, Hécate ¹ https://gitlab.haskell.org/ghc/ghc/-/issues/19884 ² https://gitlab.haskell.org/ghc/ghc/-/merge_requests/6325 ³ https://gitlab.haskell.org/ghc/ghc/-/wikis/commentary/GHCi/Tags -- Hécate ✨ 🐦: @TechnoEmpress IRC: Hecate WWW: https://glitchbra.in RUN: BSD

1 0

Extra file in GHC repo
by Simon Peyton Jones 13 May '22

13 May '22

Hi devs I've started to get this a lot bash$ git rebase origin/master First, rewinding head to replay your work on top of it... error: The following untracked working tree files would be overwritten by checkout: docs/index.html Please move or remove them before you switch branches. Aborting fatal: Could not detach HEAD Removing docs/index.html makes things work again. What am I doing wrong? Simon

2 3

stack exec -- pacman broken
by Shayne Fletcher 11 May '22

11 May '22

this isn't exactly a GHC issue but perhaps someone knows how to get it resolved? (suspecting commercial/stack i've raised [this issue]( https://github.com/commercialhaskell/stack/issues/5732) there). tl;dr `stack exec -- pacman -S ...` like commands required for building GHC on windows are broken and have been for sometime ghc-lib CI runs this command on windows, ``` stack --resolver lts-18.23 exec -- pacman -S autoconf automake-wrapper make patch python tar mintty --noconfirm ``` this normally works ok but as of today, ``` warning: database file for 'clang32' does not exist (use '-Sy' to download) warning: mintty-1~3.6.0-1 is up to date -- reinstalling error: failed to prepare transaction (could not find database) ``` in another project (ghc-lib-parser-ex), a similar command (different compiler version/stack yaml) has been producing the following reliably long enough that i'm sorry to say i just gave up testing it windows. ``` :: File /var/cache/pacman/pkg/automake1.9-1.9.6-3-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] error: automake1.10: signature from "David Macek <david.macek.0(a)gmail.com>" is unknown trust error: automake1.11: signature from "David Macek <david.macek.0(a)gmail.com>" is unknown trust error: automake1.12: signature from "David Macek <david.macek.0(a)gmail.com>" is unknown trust error: automake1.13: signature from "David Macek <david.macek.0(a)gmail.com>" is unknown trust error: automake1.14: signature from "David Macek <david.macek.0(a)gmail.com>" is unknown trust error: automake1.15: signature from "David Macek <david.macek.0(a)gmail.com>" is unknown trust :: File /var/cache/pacman/pkg/automake1.10-1.10.3-4-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] :: File /var/cache/pacman/pkg/automake1.11-1.11.6-4-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] :: File /var/cache/pacman/pkg/automake1.12-1.12.6-4-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] :: File /var/cache/pacman/pkg/automake1.13-1.13.4-5-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] :: File /var/cache/pacman/pkg/automake1.14-1.14.1-4-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] error: automake1.16: signature from "David Macek <david.macek.0(a)gmail.com>" is unknown trust error: failed to commit transaction (invalid or corrupted package) :: File /var/cache/pacman/pkg/automake1.15-1.15.1-2-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] :: File /var/cache/pacman/pkg/automake1.16-1.16.3-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). Do you want to delete it? [Y/n] Errors occurred, no packages were upgraded. ``` -- Shayne Fletcher

1 1

Gitlab problem
by Simon Peyton Jones 10 May '22

10 May '22

Friends I am abruptly unable to push or pull to the GHC repo. E.g. 'git fetch' just hangs. Yet ssh git(a)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

2 2

Deprecation process for GHC.Pack
by Hécate 09 May '22

09 May '22

Hello fellow devs, Just an email to signal the start of the deprecation process of GHC.Pack, with the three-releases cycle: 1. By prose (GHC 9.6) (#21541 <https://gitlab.haskell.org/ghc/ghc/-/issues/21541>) 2. By warning (GHC 9.8) (#21540 <https://gitlab.haskell.org/ghc/ghc/-/issues/21540>) 3. By error (GHC 9.10) (#21536 <https://gitlab.haskell.org/ghc/ghc/-/issues/21536>) You can read more about the whole thing here: https://gitlab.haskell.org/ghc/ghc/-/issues/21461 Cheers, have a nice week! -- Hécate ✨ 🐦: @TechnoEmpress IRC: Hecate WWW:https://glitchbra.in RUN: BSD

1 0