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

Parameter Limit Checking #43

Open
azriel91 opened this issue Oct 24, 2022 · 0 comments
Open

Parameter Limit Checking #43

azriel91 opened this issue Oct 24, 2022 · 0 comments

Comments

@azriel91
Copy link
Owner

azriel91 commented Oct 24, 2022

Any input / data that is reasoned upon should be sanitized, so that non-sensible values are not operated on.

The peace framework should guide implementors to define data types that have safety limits, and make it easy to do so. The framework can then use those limits to warn users when limits have been crossed.

  • Limit categories / thresholds:

    • invalid (e.g. -1 users)
    • safe / common values
    • questionable / "trust me, I know what I'm doing"
    • technically unfeasible (e.g. 5 TB RAM)
  • Warn users when using questionable values, unless they pass in a flag to silence the warning.

  • See flux

Feature gated so that framework implementors may opt-in to implementing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant