Integrate ARIEC61850 UTC-Time precision fix - #164
Merged
Conversation
Merged
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.
Purpose
Advance ARSAS from ARIEC61850 PR #54 / commit
902fc828...to the validated UTC-Time precision fix from ARIEC61850 PR #55 / commit8b46cfed....Why
ARSAS 1.6.26/1.6.27 could only receive timestamps after ARIEC61850 had already truncated sub-millisecond precision to
.fff. That made a true source around31.2006000arrive as31.200, so later seven-digit hover formatting merely produced31.2000000.Changes
8b46cfed0614a4d0b0a5bf73fa7a6e77cf6fe817/ source PR Self-host landing media and add safe Windows downloads #55;0x33 0x5A 0x86;31.2006000;31.201.Safety / scope
No FAT workflow, evidence lifecycle, multi-IED behavior, SNTP, report control, signal matching, or UI behavior is changed here. This is an engine-lock integration plus a cross-repository regression guard.
Merge only after the exact branch passes the normal ARSAS build/test/package gates, focused IO FAT validation, and deterministic SV validation.