-
Notifications
You must be signed in to change notification settings - Fork 720
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
Use patched aeson from hackage #4200
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
newhoggy
requested review from
Jimbo4350,
deepfire,
denisshevchenko,
jutaro,
mgmeier,
dcoutts,
erikd and
JaredCorduan
as code owners
July 20, 2022 04:53
erikd
approved these changes
Jul 20, 2022
Jimbo4350
approved these changes
Jul 20, 2022
newhoggy
force-pushed
the
newhoggy/use-patched-aeson-from-hackage
branch
from
July 22, 2022 01:26
6ca5373
to
a5a90ba
Compare
bors r+ |
Build succeeded: |
dermetfan
added a commit
to IntersectMBO/cardano-db-sync
that referenced
this pull request
Oct 10, 2022
nix eval .#tullia.x86_64-linux.task --apply __attrNames --impure Seems that this PR broke it: IntersectMBO/cardano-node#4200
dermetfan
added a commit
to IntersectMBO/cardano-db-sync
that referenced
this pull request
Oct 10, 2022
I also tried to update to the latest version and apply the purity fix there. However, it seems that this PR broke it (even in impure mode): IntersectMBO/cardano-node#4200 Test with: nix eval .#tullia.x86_64-linux.task --apply __attrNames --impure
dermetfan
added a commit
to IntersectMBO/cardano-db-sync
that referenced
this pull request
Oct 10, 2022
Now referencing the `backport-purity-1.35.0-rc4` branch. I also tried to update to the latest version and apply the purity fix there (`purity` branch). However, it seems that this PR broke it (even in impure mode): IntersectMBO/cardano-node#4200 Test with: nix eval .#tullia.x86_64-linux.task --apply __attrNames --impure
dermetfan
added a commit
to IntersectMBO/cardano-db-sync
that referenced
this pull request
Oct 10, 2022
Now referencing the `backport-purity-1.35.0-rc4` branch. I also tried to update to the latest version and apply the purity fix there (`purity` branch). However, it seems that this PR broke it (even in impure mode): IntersectMBO/cardano-node#4200 Test with: nix eval .#tullia.x86_64-linux.task --apply __attrNames --impure
dermetfan
added a commit
to IntersectMBO/cardano-db-sync
that referenced
this pull request
Oct 11, 2022
Now referencing the `backport-purity-1.35.0-rc4` branch. I also tried to update to the latest version and apply the purity fix there (`purity` branch). However, it seems that this PR broke it (even in impure mode): IntersectMBO/cardano-node#4200 Test with: nix eval .#tullia.x86_64-linux.task --apply __attrNames --impure
dermetfan
added a commit
to IntersectMBO/cardano-db-sync
that referenced
this pull request
Nov 10, 2022
Now referencing the `backport-purity-1.35.0-rc4` branch. I also tried to update to the latest version and apply the purity fix there (`purity` branch). However, it seems that this PR broke it (even in impure mode): IntersectMBO/cardano-node#4200 Test with: nix eval .#tullia.x86_64-linux.task --apply __attrNames --impure
dermetfan
added a commit
to IntersectMBO/cardano-db-sync
that referenced
this pull request
Nov 10, 2022
Now referencing the `backport-purity-1.35.0-rc4` branch. I also tried to update to the latest version and apply the purity fix there (`purity` branch). However, it seems that this PR broke it (even in impure mode): IntersectMBO/cardano-node#4200 Test with: nix eval .#tullia.x86_64-linux.task --apply __attrNames --impure
dermetfan
added a commit
to IntersectMBO/cardano-db-sync
that referenced
this pull request
Nov 15, 2022
Now referencing the `backport-purity-1.35.0-rc4` branch. I also tried to update to the latest version and apply the purity fix there (`purity` branch). However, it seems that this PR broke it (even in impure mode): IntersectMBO/cardano-node#4200 Test with: nix eval .#tullia.x86_64-linux.task --apply __attrNames --impure
dermetfan
added a commit
to IntersectMBO/cardano-db-sync
that referenced
this pull request
Nov 17, 2022
Now referencing the `backport-purity-1.35.0-rc4` branch. I also tried to update to the latest version and apply the purity fix there (`purity` branch). However, it seems that this PR broke it (even in impure mode): IntersectMBO/cardano-node#4200 Test with: nix eval .#tullia.x86_64-linux.task --apply __attrNames --impure
dermetfan
added a commit
to IntersectMBO/cardano-db-sync
that referenced
this pull request
Nov 17, 2022
Now referencing the `backport-purity-1.35.0-rc4` branch. I also tried to update to the latest version and apply the purity fix there (`purity` branch). However, it seems that this PR broke it (even in impure mode): IntersectMBO/cardano-node#4200 Test with: nix eval .#tullia.x86_64-linux.task --apply __attrNames --impure
dermetfan
added a commit
to IntersectMBO/cardano-db-sync
that referenced
this pull request
Nov 18, 2022
Now referencing the `backport-purity-1.35.0-rc4` branch. I also tried to update to the latest version and apply the purity fix there (`purity` branch). However, it seems that this PR broke it (even in impure mode): IntersectMBO/cardano-node#4200 Test with: nix eval .#tullia.x86_64-linux.task --apply __attrNames --impure
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that the index state has been updated, we can use the patched
aeson-2.1.0.0
from hackage instead of using our fork.This patch contains a bug fix/memory optimisation.