Aviator auto-remediation Fix#1060
Merged
Merged
Conversation
rsenden
approved these changes
Jul 22, 2026
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
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.
Summary
This change makes Aviator auto-remediation apply source edits using the encoding declared in
audit.fvdlinstead of assuming UTF-8. It reuses the existing streaming FVDL parser to read source file encoding metadata, applies strict decode/encode validation, and preserves the source file’s existing line endings when writing remediated content.https://almoctane-ams.saas.microfocus.com/ui/entity-navigation?p=206015/2001&entityType=work_item&id=2311032
fix:
fcli aviator ssc apply-remediations: apply source edits using the encoding declared inaudit.fvdlinstead of assuming UTF-8fix:
fcli fod aviator apply-remediations: apply source edits using the encoding declared inaudit.fvdlinstead of assuming UTF-8