-
Notifications
You must be signed in to change notification settings - Fork 6
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
System API for ECDSA signing #79
Conversation
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.
LGTM!
I'll help with fixing CI.
This comment was marked as outdated.
This comment was marked as outdated.
… OOM I've seen GHC require >16GB of RES while GitHub runners only have 7GB of RAM.
We're noticing that on #79 GHC requires massive amounts of memory to build certain modules (`IC.Test.Agent` being the worst offender requiring more than 13GB while GitHub Runners only have 7GB causing OOM kills). What's worse is that multiple components in the cabal file require the same modules causing the same module to be build multiple times, often in parallel exacerbating the memory problem. This fixes the duplicate compilation issue by letting the components in the cabal file only depend on the ic-hs library. This might be deterimental to ghcid as mentioned in the cabal file. But the associated ticket has been closed so the problem is hopefully fixed in an upcoming GHC release.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Status reportFor building See: NixOS/nixpkgs#61575 For this reason I had to remove TemplateHaskell support from QuickCheck. But Not yet sure how to work around this... |
The TemplateHaskell issues have been fixed by patching GHC and disabling haddock in a few libraries. Now hopefully the last remaining issue is the following error when building
@nomeata mentioned a similar issue in rethab/bindings-dsl#38. |
So maybe 47e1274 cab be cherry-picked? |
I think |
This reverts commit 3dc3072.
due to rethab/bindings-dsl#38 Originally dfinity-lab/ic-ref@c6ae6a9
Next problem is that The reason is that the
Note that the references to |
@nomeata any idea how these paths to warp end up in |
Just linking NixOS/nixpkgs#43795 (comment) here because I think we can simplify our static linking setup when we upgrade to release-22.05 (like removing our GHC override). |
If these paths are actually unused and don’t affect whether it runs, you can use I guess they are there because warp uses the
|
On our way to the cinema to see Top Gun my brother @roelvandijk and I came to the same conclusion when discussing this problem ;) Thanks for confirming our hypothesis! I'll remove the references with |
This PR Implements a corresponding part of the IC spec: dfinity/interface-spec#6
It also splits up
IC.Test.Agent
andIC.Test.Spec
to reduce the excessive memory consumption of compiling those modules.