Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[PICS-Removal] Removing automatable PICS from ICDM 2 1 test module #34933
base: master
Are you sure you want to change the base?
[PICS-Removal] Removing automatable PICS from ICDM 2 1 test module #34933
Changes from 13 commits
eb00219
f74cdc7
38cdc25
dd77706
355e460
372e144
6f9e1e5
076cbe6
267afbe
fa944cd
a629150
07bb37a
d7747ed
0d62747
fcb86b7
969a87f
4618ff4
2a59997
0eb6b99
1b63d63
545232f
ddb3488
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
thinking it makes more sense to have this be a non-async function. See _async_runner for the wrapper on how to do that. I don't think you're ever going to want this to be truly async
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.
It does seem that it makes more sense for it to be non-async, always best to keep things as simple as possible.
Updated using _async_runner as an example, created async_function_runner function in matter_testing support module, this should allow us to call the functions such as attribute_guard inside of tests without having to use await moving forward, instead uses the asyncio.wait_for() and asyncio.run() as needed such as displayed in _async_runner.
Please let me know if this will be ok.