-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement support for Aeson-2.2.3 #252
base: master
Are you sure you want to change the base?
Conversation
Yeah, exactly. I disabled this just so I could get the branch to compile. I
will delete it from the PR now.
…On Thu, Aug 1, 2024, 19:22 j6carey ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In stack.yaml
<#252 (comment)>
:
>
nix:
packages:
- zlib.dev
- zlib.out
+
+
+flags:
+ proto3-suite:
+ large-records: False
+ dhall: False
To answer my own question: probably it's an issue with dhall and the GHC
9.8 compiler or dependencies.
—
Reply to this email directly, view it on GitHub
<#252 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABSCVAUI2S2ODDBIQD5WTQLZPJVFRAVCNFSM6AAAAABL2A3ZF6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDEMJTGQZDIOJQGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
There's some hope that as the toolchain evolves we will be able to support dhall once again for GHC 9.8. |
@tonyalaribe , we are investigating the mysterious CI failure. |
proto3-suite.cabal
Outdated
@@ -103,6 +103,7 @@ library | |||
build-depends: aeson >= 1.1.1.0 && < 2.2, | |||
aeson-pretty, | |||
attoparsec >= 0.13.0.1, | |||
attoparsec-aeson, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is attoparsec-aeson
used for? If we absolutely must depend on attoparsec-aeson
then can we have bounds added?
@tonyalaribe , CI seems to be working again. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add bounds on the attoparsec-aeson
package and we can merge this.
Thanks! I've pushed an update with the bounds |
From the CI failures, my guess is that we will have to make the mention of |
@tonyalaribe , could you merge branch "master" into your PR? There have been some recent changes to the Nix environment that might be relevant. |
@j6carey The branch is up to date with master |
I'm not so familiar with nix, so i'm having trouble debugging the issue with the CI |
My mistake; when I checked for that I was looking at the wrong PR. Sorry for the confusion. I'll look into the build issues. |
@tonyalaribe , could you try the following changes to avoid the build failures for older package sets that lack
Apply this patch:
|
No description provided.