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

Add custom input policy test #8800

Merged
merged 6 commits into from
May 24, 2024
Merged

Add custom input policy test #8800

merged 6 commits into from
May 24, 2024

Conversation

IonesioJunior
Copy link
Member

Description

This PR aims to fix CustomInputPolicy creation and usage workflow and add a new test in custom-policy notebook.

Affected Dependencies

List any dependencies that are required for this change.

How has this been tested?

  • Describe the tests that you ran to verify your changes.
  • Provide instructions so we can reproduce.
  • List any relevant details for your test configuration.

Checklist

Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

# Tech debt : For input policies, we required to have NodeIdentity args beforehand,
# therefore at this stage we had to return back to the normal args.
# Maybe there's better way to do it.
if len(init_args) and isinstance(list(init_args.keys())[0], NodeIdentity):
Copy link
Member

Choose a reason for hiding this comment

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

Depending on how urgent this is, could we maybe fix this tech debt? I was thinking over the weekend that maybe this will affect other parts of the codebase, and the solution here is pretty dirty

Copy link
Member Author

Choose a reason for hiding this comment

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

Risk level is labeled as high in our spreadsheet. So, I'm guessing its important, but I can't tell how urgent it is. So maybe we can check @madhavajay opinion on it.

But I'm all for looking a cleanest solution. In fact I'd like to refactor a bit the way policies are designed, as we discussed last friday, the workflow is complex and has plenty of indirect effects. But this would require this task to be medium-high size. Do you have any new opinions/ideas on that @teo-milea?

@teo-milea teo-milea merged commit cb6dfe6 into dev May 24, 2024
26 checks passed
@teo-milea teo-milea deleted the add_custom_input_policy_test branch May 24, 2024 04:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants