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
Resolve Visibility of Aggregator Private Attributes in Experimental Workflow #1084
Resolve Visibility of Aggregator Private Attributes in Experimental Workflow #1084
Changes from all commits
544cdd2
49eac51
a827774
5d308cd
dbe8b1e
461247d
58b5d16
abdd735
8323ed9
fbeb05b
188adff
44ab058
547bfca
a8596bb
0e96228
4c06768
2d0a1c9
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.
If we remove the private attribute filtering from here, then who is responsible for doing it, especially if we execute the FLSpec via the
run()
method, rather than through the export feature?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.
Private attribute filtering is required while transitioning from aggregator to collab (and vice-versa). For
LocalRuntime
it is done inside Participants (openfl/experimental/interface/participants.py) and inFederatedRuntime
it is done inside Component (openfl/experimental/component/aggregator/aggregator.py and openfl/experimental/component/collaborator/collaborator.py)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.
I see, thanks for the explanation, @refai06 - the distinction is indeed not obvious for the "uninitiated" reader...
As a follow-up PR, I'd suggest re-organizing a little bit the code, to make it easier to navigate and review. Right now, everything related to Workflow API resides directly under
openfl/experimental
- thus implicitly "disallowing" other experimental features. Instead, it may be better to have a dedicatedopenfl/experimental/workflow
package for example. Additionally, underopenfl/experimental/workflow
, we could imagine separate sub-packages forlocal
,federated
andexport
for example.WDYT?