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

Harmonize Error Message #83

Open
sbckr opened this issue Dec 18, 2024 · 0 comments
Open

Harmonize Error Message #83

sbckr opened this issue Dec 18, 2024 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@sbckr
Copy link
Member

sbckr commented Dec 18, 2024

When executing MPC Programs, computation may fail for players with different reasons. However, user will only be prompted one of the received error messaged, not allowing him to gain more insights into the issue causing the error.

E.g.
When ephemeral programs are executed and a game starts, some parties will try to establish connections for interim-data exchange to other players as of communication managed implemented in MP-SPDZ. These players might wait for the connections to be established and fail after a given timeout. If the program was triggered with a potential input it is unauthorized to access, some players may (more or less) immediately fail with error unauthorized. Still, the client will only receive one of the error messages.

One should either implement error handling such that all error received are printed, or better make sure that players fail for the same reason.

@sbckr sbckr added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

1 participant