Skip to content

Fix: Negative thresholds interpreted as argument #550

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
merged 1 commit into from
Aug 24, 2022

Conversation

LordHepipud
Copy link
Collaborator

Fixes negative thresholds being interpreted wrongly as argument instead of an value for an argument

Fixes #528

@cla-bot cla-bot bot added the cla/signed label Aug 22, 2022
@LordHepipud LordHepipud self-assigned this Aug 22, 2022
@LordHepipud LordHepipud added the Bug There is an issue present label Aug 22, 2022
@LordHepipud LordHepipud added this to the v1.10.0 milestone Aug 22, 2022
@LordHepipud LordHepipud merged commit 4c5eeaf into master Aug 24, 2022
@LordHepipud LordHepipud deleted the fix/negative_thresholds_interpreted_as_argument branch August 24, 2022 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug There is an issue present cla/signed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Problem with negative threshold range when using REST-API
1 participant