-
Notifications
You must be signed in to change notification settings - Fork 1.2k
fix(framework): Report clientapp appio communication failures as errors #7061
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
Merged
danieljanes
merged 51 commits into
main
from
report-clientapp-appio-communication-failures-as-errors
May 6, 2026
+62
−4
Merged
Changes from all commits
Commits
Show all changes
51 commits
Select commit
Hold shift + click to select a range
0d37584
init
panh99 39d56b3
mv util
panh99 b35431b
tweak
panh99 6d43b39
tweak
panh99 cf0e4a8
Merge branch 'main' into rt-cert-for-apps
panh99 110869d
address comments
panh99 bc99645
Merge branch 'main' into rt-cert-for-apps
panh99 8b3fc32
Merge branch 'main' into rt-cert-for-apps
jafermarq 059aaeb
post-merge format
jafermarq 7f80179
Update framework/py/flwr/supercore/tls.py
jafermarq 6852c8a
fix
jafermarq 7367ebc
Merge branch 'main' into rt-cert-for-apps
jafermarq 1137cd3
Merge remote-tracking branch 'origin/main' into rt-cert-for-apps
panh99 f19ee02
fix merge
panh99 42cd228
fix
panh99 f81c952
address comments
panh99 b99fd3e
rename
panh99 49da492
./dev/format.sh
panh99 acc1e95
Merge branch 'main' into rt-cert-for-apps
panh99 0dcb752
Merge branch 'main' into rt-cert-for-apps
msheller 686b20a
Merge branch 'main' into rt-cert-for-apps
msheller 4977afd
initial server-side TLS implementation
msheller 543add2
second codex pass to tighten/simplify
msheller b6568dd
Merge branch 'main' into tls-for-appio-servicers
msheller 1c1f758
Merge branch 'main' into rt-cert-for-apps
msheller 3a74302
Merge branch 'rt-cert-for-apps' into tls-for-appio-servicers
msheller f5ce749
removed unneeded refactoring to minimize review delta
msheller 69b749d
formatting and testing fixes
msheller 21f4c8a
improved comments
msheller 07b50ae
fix to use option 2 (seperate certs)
msheller eb3dcb7
added helpers for run_superlink to dramatically simplify tests
msheller 223307a
expands cert paths before file check
msheller 1cd6e4b
appio tls no longer required when fleet API tls is used
msheller 6eda1e3
Merge branch 'main' into rt-cert-for-apps
panh99 3dc0346
Merge branch 'main' into tls-for-appio-servicers
msheller a61d303
Addressed comments from code reviewers
msheller 92f0ac4
Merge remote-tracking branch 'origin/rt-cert-for-apps' into tls-for-a…
msheller e7f9c6a
ready for manual review
msheller f0e1c7d
Merge branch 'main' into tls-for-appio-servicers
msheller 57b0f2f
docstrings updated to address latest codex review comment
msheller 64eeabe
fixed merge conflict regression
msheller c7d2fcc
Merge branch 'tls-for-appio-servicers' into report-clientapp-appio-co…
msheller ded519d
Merge branch 'main' into report-clientapp-appio-communication-failure…
panh99 3cb6210
formatting fixes
msheller 8414a66
Merge branch 'main' into report-clientapp-appio-communication-failure…
msheller aeac3c3
Error message text consistency improvement
msheller 1594c93
Merge branch 'main' into report-clientapp-appio-communication-failure…
msheller e5b3597
Merge branch 'main' into report-clientapp-appio-communication-failure…
msheller 9ab5cc2
updated exit code 250 docs
msheller 15e5d9b
removed erroneous (edited) text in 250.rst
msheller 8c7ae8c
Merge branch 'main' into report-clientapp-appio-communication-failure…
panh99 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| ##################################### | ||
| [250] CLIENTAPP_COMMUNICATION_ERROR | ||
| ##################################### | ||
|
|
||
| ************* | ||
| Description | ||
| ************* | ||
|
|
||
| During a run, the internal ClientApp process could not communicate with the SuperNode | ||
| ClientAppIo API. | ||
|
|
||
| **************** | ||
| How to Resolve | ||
| **************** | ||
|
|
||
| Check the run output and the surrounding SuperNode and SuperExec process logs for the | ||
| underlying gRPC error. By default, these processes log to stdout/stderr; in | ||
| containerized deployments, inspect the relevant SuperNode and SuperExec pod/container | ||
| logs. | ||
|
|
||
| A likely cause is that the ClientApp process took too long to start, for example on a | ||
| very slow or overloaded system, causing a timeout error. If the logs are not enough to | ||
| diagnose the issue, contact the Flower team and include the relevant run, SuperNode, and | ||
| SuperExec/ClientApp logs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
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.
The implementation looks good to me, but I think the new exit-code docs are a little too user-action-oriented for an internal process. In normal runtime usage, users do not start
flwr-clientappdirectly; it is launched by SuperExec with the AppIO address/token/TLS settings already derived from the SuperNode/SuperExec setup.Could we adjust this page to say that this means the internal ClientApp process (
flwr-clientapp) could not communicate with the SuperNode ClientAppIo API, and that users should check the surrounding SuperNode/ClientApp logs for the underlying gRPC error? A likely cause is that the ClientApp process took too long to start, for example on a very slow or overloaded system, causing the short-lived token/heartbeat window to expire. If the log message is not enough to diagnose it, users should contact the Flower team with the relevant logs. Wdyt?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.
Updated! LMK if you want further changes!