From andrew.lelechenko at gmail.com Thu Jan 5 01:06:38 2023 From: andrew.lelechenko at gmail.com (Andrew Lelechenko) Date: Thu, 5 Jan 2023 01:06:38 +0000 Subject: CLC Election January 2023 Message-ID: The terms of three CLC members are ending in January, so we are seeking new nominations! # Who should apply? Anyone who meets the following criteria should apply: * Candidates should have enough bandwidth to review merge requests to `base` on a semi-frequent basis (3 to 5 per month), and sustain this for their 3 years term in a healthy manner. * Candidates should be able to contribute opinions and analysis to issues raised by the community as a part of the CLC proposal process on a semi-frequent basis (3 to 5 per month). * Candidates should be good communicators, and at least be able to articulate to the CLC team when they will be available vs. unavailable. * Candidates should be productive, and be able to follow through on merge requests and conversations to their completion in a diligent and timely manner. We encourage any and all who satisfy these requirements to apply. Please note that we are not looking for the biggest galaxy brain in the room - quite the opposite. We are looking for productive, motivated individuals who want to help support the ecosystem that we love. As such, we hope to build a broad sample of the community. # How can I apply? To apply for one of these positions, send an email to clc.nominations.2023 at gmail.com that consists of the following data: * The header “CLC Election January 2023 - {your name}”. * Why you think you’re a good fit given the above criteria. * If applicable, please point us to some code you’ve written. Please apply before Feb 1. Best regards, Andrew From clyring at gmail.com Thu Jan 12 21:49:41 2023 From: clyring at gmail.com (Matthew Craven) Date: Thu, 12 Jan 2023 16:49:41 -0500 Subject: [ANN] bytestring-0.11.4.0 Message-ID: On behalf of the maintainers team I'm happy to announce that bytestring-0.11.4.0 (http://hackage.haskell.org/package/bytestring-0.11.4.0) is finally released. Highlights from the changelog ( https://github.com/haskell/bytestring/blob/0.11.4.0/Changelog.md): * A serious bug in `instance Lift ShortByteString` has been fixed. * `Builder` literals no longer break `warp` versions older than 3.3.22 by demanding too large of a buffer. * `unsafeIndex` is once again exported from Data.ShortByteString.Internal. * Many operations on `ShortByteString` have been made much more efficient. Many people contributed their time and effort to make this release happen. Thanks to all of them! Just to name a few, in no particular order: * Alexander Biehl * Xia Li-yao * Sergey Vinokurov * Viktor Dukhovni * Julian Ospald * Andreas Klebinger * Simon Jakobi * Andrew Lelechenko * every contributor to the older bytestring releases Happy Haskelling! ~-Matthew Craven (Hopefully the send is successful this time!) -------------- next part -------------- An HTML attachment was scrubbed... URL: From hasufell at posteo.de Fri Jan 13 04:28:56 2023 From: hasufell at posteo.de (Julian Ospald) Date: Fri, 13 Jan 2023 04:28:56 +0000 Subject: [ANN] bytestring-0.11.4.0 In-Reply-To: References: Message-ID: <8f2cd6a8-5aeb-2e69-01d9-f8ec2ee85172@posteo.de> Hi, I tried to get a reference to the Lift instance bug of ShortByteString, but I couldn't. All I see is the switch to ByteArray: https://github.com/haskell/bytestring/commit/91a727c2e52b13e4ad259293ed0024531ce48d85 What was the bug? Cheers On 1/13/23 05:49, Matthew Craven wrote: > On behalf of the maintainers team I'm happy to announce that > bytestring-0.11.4.0 > (http://hackage.haskell.org/package/bytestring-0.11.4.0 > ) is finally > released. > Highlights from the changelog > (https://github.com/haskell/bytestring/blob/0.11.4.0/Changelog.md > ): > > * A serious bug in `instance Lift ShortByteString` has been fixed. > * `Builder` literals no longer break `warp` versions older than 3.3.22 > by demanding too large of a buffer. > * `unsafeIndex` is once again exported from Data.ShortByteString.Internal. > * Many operations on `ShortByteString` have been made much more efficient. > > Many people contributed their time and effort to make this release > happen. Thanks to all of them! Just to name a few, in no particular order: > > * Alexander Biehl > * Xia Li-yao > * Sergey Vinokurov > * Viktor Dukhovni > * Julian Ospald > * Andreas Klebinger > * Simon Jakobi > * Andrew Lelechenko > * every contributor to the older bytestring releases > > Happy Haskelling! > ~-Matthew Craven > > (Hopefully the send is successful this time!) > > > _______________________________________________ > Libraries mailing list > Libraries at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries From clyring at gmail.com Fri Jan 13 12:21:10 2023 From: clyring at gmail.com (Matthew Craven) Date: Fri, 13 Jan 2023 07:21:10 -0500 Subject: [ANN] bytestring-0.11.4.0 In-Reply-To: <8f2cd6a8-5aeb-2e69-01d9-f8ec2ee85172@posteo.de> References: <8f2cd6a8-5aeb-2e69-01d9-f8ec2ee85172@posteo.de> Message-ID: This was the first item in the main changelog, which provided a link. See: * https://github.com/haskell/bytestring/pull/542 * https://github.com/haskell/aeson/issues/967 * https://gitlab.haskell.org/ghc/ghc/-/issues/22204 In short, if Lift was used to produce two ShortByteStrings that have the same length, then GHC would sometimes use the same buffer for both when the code actually gets run. It's pretty bad. Thanks for asking. On Thu, Jan 12, 2023 at 11:29 PM Julian Ospald wrote: > > Hi, > > I tried to get a reference to the Lift instance bug of ShortByteString, > but I couldn't. > > All I see is the switch to ByteArray: > https://github.com/haskell/bytestring/commit/91a727c2e52b13e4ad259293ed0024531ce48d85 > > What was the bug? > > Cheers > > On 1/13/23 05:49, Matthew Craven wrote: > > On behalf of the maintainers team I'm happy to announce that > > bytestring-0.11.4.0 > > (http://hackage.haskell.org/package/bytestring-0.11.4.0 > > ) is finally > > released. > > Highlights from the changelog > > (https://github.com/haskell/bytestring/blob/0.11.4.0/Changelog.md > > ): > > > > * A serious bug in `instance Lift ShortByteString` has been fixed. > > * `Builder` literals no longer break `warp` versions older than 3.3.22 > > by demanding too large of a buffer. > > * `unsafeIndex` is once again exported from Data.ShortByteString.Internal. > > * Many operations on `ShortByteString` have been made much more efficient. > > > > Many people contributed their time and effort to make this release > > happen. Thanks to all of them! Just to name a few, in no particular order: > > > > * Alexander Biehl > > * Xia Li-yao > > * Sergey Vinokurov > > * Viktor Dukhovni > > * Julian Ospald > > * Andreas Klebinger > > * Simon Jakobi > > * Andrew Lelechenko > > * every contributor to the older bytestring releases > > > > Happy Haskelling! > > ~-Matthew Craven > > > > (Hopefully the send is successful this time!) > > > > > > _______________________________________________ > > Libraries mailing list > > Libraries at haskell.org > > http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries > _______________________________________________ > Libraries mailing list > Libraries at haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/libraries From carter.schonwald at gmail.com Mon Jan 23 18:37:22 2023 From: carter.schonwald at gmail.com (Carter Schonwald) Date: Mon, 23 Jan 2023 13:37:22 -0500 Subject: whither the maintainer for comp-data? request for NMU? Message-ID: Hey everyone, https://github.com/pa-ba/compdata/issues/36 and many similar issues and 1-3 corresponding PRs have been posted to the comp-data repo, whats the current process for engaging the trustees in making an NMU that handles newer ghc support? (these issues have been standing for ~ a year now). ideally the maintainer surfaces in the near future, but would be great to get it buildable again -Carter -------------- next part -------------- An HTML attachment was scrubbed... URL: