Expose final_stop_active? for diagnostic sampling#35
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Maakt
Zaptec::State#final_stop_active?publiek zodat clients deze waarde los kunnen uitlezen, naastpaused?.Achtergrond: bij sessie 1098126 bleef de charger in
Connected_Requestinghangen zonder vermogen. We vermoeden datFinalStopActivedaarbij nog op 1 stond (wat een uitgebreidepaused?-definitie rechtvaardigt), maar kunnen dat nu niet bevestigen omdat we die vlag niet apart vastleggen. Doorfinal_stop_active?publiek te maken kan StekkerWeb de waarde meesamplen incharging_connector_states.Geen gedragswijziging —
paused?blijft ongewijzigd./cc @martijnversluis