Skip to content
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

Include ledger specifier when writing keys in a JSON file #711

Merged
merged 5 commits into from
Jan 23, 2024

Conversation

angrybayblade
Copy link

Proposed changes

Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.

Fixes

If it fixes a bug or resolves a feature request, be sure to link to that issue.

Types of changes

What types of changes does your code introduce to agents-aea?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply.

  • I have read the CONTRIBUTING doc
  • I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.
  • Lint and unit tests pass locally with my changes and CI passes too
  • I have added tests that prove my fix is effective or that my feature works
  • I have checked that code coverage does not decrease.
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in downstream modules

Comment on lines +169 to +171
key_pairs.append(
{ADDRESS: crypto.address, PRIVATE_KEY: priv_key, LEDGER: type_}
)
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This ledger specifier will be used by the deployment builder to write keys for the agents. The solana deployments failed because the deployment builder was writing solana keys as ethereum keys since there was no specifier in the keys.json file.

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (d12acd2) 90.25% compared to head (128e768) 90.26%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #711      +/-   ##
==========================================
+ Coverage   90.25%   90.26%   +0.01%     
==========================================
  Files         371      371              
  Lines       29816    29817       +1     
==========================================
+ Hits        26910    26914       +4     
+ Misses       2906     2903       -3     
Flag Coverage Δ
unittests 90.26% <100.00%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

dvilelaf
dvilelaf previously approved these changes Jan 23, 2024
Adamantios
Adamantios previously approved these changes Jan 23, 2024
@angrybayblade angrybayblade merged commit ab6024f into main Jan 23, 2024
35 of 36 checks passed
@DavidMinarsch DavidMinarsch deleted the feat/ledger-specifier branch January 30, 2024 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants