-
Notifications
You must be signed in to change notification settings - Fork 63
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
AEA-245 AEA-244 AEA-225 Adding protocol generator to the CLI tool #605
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.
Great work as a first step. Please consider my comments and add some tests for the new command.
…hortening error checking code in protocol template class; replacing 0.1.0 with a constant DEFAULT_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.
Thanks for the changes, spotted a few more suggestions.
…otocolConfig object; Addresses second bacth of comments in PR; changing authors->author; license_config->license; moved sample_proto_spec file to new location;
…acting its fields using ProtocolConfig objects;
…elCase for class names; list of contents -> dictionary of contents and styled;
… tests pass; CURRENTLY: 1 test does not pass (commented); Not sure about the validity of TestGenerateProtocolFailsWhenExceptionOccurs, although it passes;
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.
Great work on tests! I have some comments re the protocols we generate. We can improve the formatting and make sure they are mypy/flake8 compliant. We need to fix the contents
argument. A list won't work as we have a dict
elsewhere in speech_acts so there is no ordering.
if message_id == 1: | ||
assert target == 0, "target should be 0" | ||
else: | ||
assert 1 < target < message_id, "target should be between 1 and message_id" |
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.
assert 0 < target < message_id, "target should be strictly between 0 and message_id"
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.
Only the first message's target can be 0 (i.e. targets nothing since first move).
The other moves must target an existing one (i.e. 1 < target < message_id).
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.
Yes, but your code excludes target=1
which is a valid target for a message_id > 1
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
Adding the protocol generator form the agents-research repository to the this repository.
Adding protocol generation as an option in the CLI tool.
Fixes #521, #556, #557
Types 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
.aea cli
tool worksFurther comments
Work in progress...