-
Notifications
You must be signed in to change notification settings - Fork 16
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
ACN to valory + docs #95
Conversation
ce23608
to
bd5a01a
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.
Now there's an issue on golang tests. I'll let you fix them.
tests/test_packages/test_connections/test_p2p_libp2p_client/test_communication.py
Outdated
Show resolved
Hide resolved
80d1a64
to
6a5b8b9
Compare
708db18
to
8805548
Compare
Codecov Report
@@ Coverage Diff @@
## main #95 +/- ##
==========================================
+ Coverage 96.89% 96.92% +0.03%
==========================================
Files 307 301 -6
Lines 24258 23920 -338
==========================================
- Hits 23504 23185 -319
+ Misses 754 735 -19
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
from google.protobuf.struct_pb2 import ( # pylint: disable=no-name-in-module | ||
ListValue, | ||
Struct, | ||
) |
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.
Is # pylint: disable=no-name-in-module
required after pinning protobuf
version?
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.
No it's not required anymore
with: | ||
go-version: "^1.14.0" | ||
go-version: "1.17.7" |
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.
We use different versions throughout this file. That's not desirable. I propose we use >=1.14.0 <=1.17.0
throughout as this makes explicit the ranges for which it works.
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.
Feel free to open an issue for it.
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
Proposed changes
Fixes
p2p_libp2p*
connection versions to 0.1.0Types of changes
What types of changes does your code introduce to agents-aea?
Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply.develop
branch (left side). Also you should start your branch off ourdevelop
.Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...