-
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
Update to cardano-api-8.8.0.0
and cardano-cli
#5383
Conversation
cardano-api-8.8.0.0
and cardano-cli
5741a2b
to
196afbe
Compare
80e446a
to
8947513
Compare
02c44d4
to
ce2d3be
Compare
d9a910c
to
b325a1d
Compare
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.
Regarding my changes LGTM!
721aec6
to
142e404
Compare
3f2a77e
to
cd2c174
Compare
cabal.project
Outdated
@@ -108,3 +108,39 @@ package snap-server | |||
-- IMPORTANT | |||
-- Do NOT add more source-repository-package stanzas here unless they are strictly | |||
-- temporary! Please read the section in CONTRIBUTING about updating dependencies. | |||
|
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.
Are these things not yet in CHaP?
Is it worth waiting until they are?
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.
I should probably not have been looking at each commit individually. However, I do also think that the commit history should be cleaned up so that it looks like those SRPs were never added.
cd2c174
to
630dd10
Compare
Currently, Hydra CI reports a compilation error for |
630dd10
to
08ba49b
Compare
…ano-cli-8.3.0.0 Set initial block forging Moved UseLedger type to avoid circular imports - The moving of UseLedger was needed in order to import `Cardano.Node.Protocol (ProtocolInstantiationError)` - Added new constructors to Startup Tracer Update block forging configuration on SIGHUP Block Forging can be enabled/disabled through SIGHUP signal. Sending such a signal will trigger the node to read the block forging credential files. Since the credential files are passed via CLI flags one can not remove them without restarting the node. For this effect, in order for one to be able to disable block forging, moving/renaming/deleting the file at the specified path (for the credential flags) and then sending the SIGHUP signal is what needs to be done. The code will detect that the specified files do not exist and it will disable block forging, while tracing the appropriate log messages. In case one wants to start a block producing node (i.e. passing the credentials in the respective flags) but doesn't want it to actually behave as a BP, there's a new `--start-as-non-producing-node` flag that will run the node with credentials as a normal node. However on SIGHUP it will read the credential files and start forging. Refactor code to accomodate the changes Added EnabledBlockForging type Fix Shutdown test for new exit codes Co-authored-by: Armando Santos <armandoifsantos@gmail.com> Co-authored-by: Jordan Millar <jordan.millar@iohk.io> Co-authored-by: Marcin Szamotulski <coot@coot.me> Co-authored-by: Samuel Leathers <samuel.leathers@iohk.io>
08ba49b
to
eb66a54
Compare
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.
Thanks @newhoggy LGTM!
Description
Note,
cardano-api-8.8.0.0
doesn't exist yet, but will be published soon.Checklist
See Runnings tests for more details
CHANGELOG.md
for affected package.cabal
files are updatedhlint
. See.github/workflows/check-hlint.yml
to get thehlint
versionstylish-haskell
. See.github/workflows/stylish-haskell.yml
to get thestylish-haskell
versionghc-8.10.7
andghc-9.2.7
Note on CI
If your PR is from a fork, the necessary CI jobs won't trigger automatically for security reasons.
You will need to get someone with write privileges. Please contact IOG node developers to do this
for you.