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

Fix device messages #216

Merged
merged 2 commits into from Oct 20, 2021
Merged

Fix device messages #216

merged 2 commits into from Oct 20, 2021

Conversation

Flix6x
Copy link
Contributor

@Flix6x Flix6x commented Oct 20, 2021

Fixes cases where data retrieved from the database isn't already chronologically ordered. This bug caused device messages to possibly state a negative duration (in case the last value preceded the first one).

@Flix6x Flix6x self-assigned this Oct 20, 2021
@Flix6x Flix6x added API bug Scheduling labels Oct 20, 2021
@Flix6x Flix6x requested a review from nhoening Oct 20, 2021
@Flix6x Flix6x merged commit f4a2a41 into main Oct 20, 2021
2 checks passed
@Flix6x Flix6x deleted the fix-device-messages branch Oct 20, 2021
Flix6x added a commit that referenced this issue Oct 20, 2021
Fix cases where data retrieved from the database isn't already chronologically ordered. This bug caused device messages to possibly state a negative duration (in case the last value preceded the first one).

* Order power values chronologically in device messages

* Changelog entry
@Flix6x Flix6x added this to the 0.6.1 milestone Jan 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API bug Scheduling
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants