fix: make sure privileged commands can run when there is a space in the spec or support file name #31001
+14
−1
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.
Additional details
With the release of Cypress 14, some of the logic around stack lines and traces changed. One thing we forgot to check for when matching script to stack traces lines is whether both strings are encoded the same way. The stack trace URLs are URI encoded, but the script files are not. This means that if there is a space or unicode character in the file name we will not be able to correctly match the command invocation destination, which throws the error.
Before fix
After fix
Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?