fix: use WriteAllText with UTF8NoBOM in Register-AntigravityMcp (#410) - #411
Closed
rafaio1 wants to merge 1 commit into
Closed
fix: use WriteAllText with UTF8NoBOM in Register-AntigravityMcp (#410)#411rafaio1 wants to merge 1 commit into
rafaio1 wants to merge 1 commit into
Conversation
Set-Content -Encoding UTF8 writes a BOM (EF BB BF) on Windows PowerShell 5.1, which breaks JSON parsers that don't expect it. Replace with [System.IO.File]::WriteAllText using UTF8Encoding($false) to emit clean UTF-8. Fixes monk-io#410 Payout: 877hj5d4ya4N2B5gPsazm1dudN61Fkjz1V9izhD5m2TU (Solana)
Member
|
Closing this one — #368 covers the same fix for #367/#410 and is the version we're taking forward. Thanks for taking a look. A note for future submissions: please don't put payment or wallet addresses in pull request descriptions. Bounty scoring and any payout are handled through the process described in the bounty rules, never through details posted in a PR. |
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
2 participants
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
Fixes #410
Set-Content -Encoding UTF8writes a UTF-8 BOM (EF BB BF) on Windows PowerShell 5.1, which breaks JSON parsers that do not expect it. This PR replaces the call with[System.IO.File]::WriteAllTextusingUTF8Encoding($false)to emit clean UTF-8 without BOM across all three copies ofstart-monk-agent.ps1.Changes
scripts/start-monk-agent.ps1line 164plugins/monk/scripts/start-monk-agent.ps1line 164.antigravity-plugin/scripts/start-monk-agent.ps1line 164Verification
The fix uses the same pattern recommended by Microsoft for BOM-free UTF-8 output in Windows PowerShell 5.1 and is compatible with PowerShell 7+.
Payout: 877hj5d4ya4N2B5gPsazm1dudN61Fkjz1V9izhD5m2TU (Solana)