🐛 Fix VBScript quote escaping in launcher files (use \"\" not \\\")#93
Merged
🐛 Fix VBScript quote escaping in launcher files (use \"\" not \\\")#93
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
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.
What does this PR do?
Fixes invalid VBScript quote escaping introduced in PR #92. The previous fix used
\"(backslash-quote) to embed double-quotes inside the VBScript string — that is C/JSON-style escaping and is not valid VBScript syntax.wscript.exewas silently running a malformed command (the backslashes were passed literally to the shell, causing pwsh to fail to launch).Correct VBScript escaping uses
""(two consecutive double-quotes) to represent a single literal".Before:
After:
The resulting command passed to the shell is now correctly:
Files changed:
Scripts/iKAT/Invoke-FFmpegCapture/Start-DinaRecording.vbsScripts/iKAT/Invoke-FFmpegCapture/Start-JoeyRecording.vbsWhy are we doing this?
After merging #92, manual testing showed a
wscript.exeprocess launching indpuerner's session but nopwsh.exestarting and no debug log entry — confirming the VBS was running but the command was malformed. The\"sequences caused the shell to receive literal backslashes before the path, preventing pwsh from resolving.How should this be tested?
git pullStop-Process -Name wscript -ForceStart-ScheduledTask -TaskName "iKAT-Record-Dina"(whiledpuerneris logged on)dpuerner_*.tsfile appears inC:\RecordingsC:\Recordings\debug.logforScript started. USERNAME=dpuernerAny deployment notes?
Pull on server and kill the currently hanging wscript instance from the previous broken run: