We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nspawn
The pathname parsing in nspawn function does not take into consideration spaces in the pathname.
Consider the following pathname of a CLI application: /home/user/Project Folder/Sub Folder/bin/cli (note the spaces in the pathname)
/home/user/Project Folder/Sub Folder/bin/cli
In the lines 360-362 in nexpect.js, we can see the following code:
nexpect.js
/home/user/Project
params
[ "Folder/Sub" , "Folder/bin/cli" ]
This leads to improper pathanme parsing and errors in testing.
The pathname should be parsed properly even if it contains spaces in it.
The text was updated successfully, but these errors were encountered:
A detailed description of this issue can be found here: aws-amplify/amplify-cli#7324
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Bug Description:
The pathname parsing in
nspawn
function does not take into consideration spaces in the pathname.Consider the following pathname of a CLI application:
/home/user/Project Folder/Sub Folder/bin/cli
(note the spaces in the pathname)In the lines 360-362 in
nexpect.js
, we can see the following code:Suppose we consider our above pathname, we can clearly observe:
/home/user/Project
params
OR[ "Folder/Sub" , "Folder/bin/cli" ]
This leads to improper pathanme parsing and errors in testing.
Expected Behaviour:
The pathname should be parsed properly even if it contains spaces in it.
The text was updated successfully, but these errors were encountered: