Closed vonguyenminhtu2504 closed 7 months ago
Thanks for reporting! I'm not so sure what to do here unfortunately. I only have a mac, and I tested from a directory with a space, and the test ran fine. I don't see the stack trace even crossing the application at any point either, just a bunch of lines from node:internal. To some degree, I feel like I'm not confident this even involves selenium-side-runner.
For example, it closely matches this error someone talked about getting for react-scripts:
Here are some people talking about this in node core:
https://github.com/nodejs/help/issues/2644
It seems like the special characters thing is more of a core nodejs issue than a selenium-side-runner issue, and I'm not at the level of fixing issues in the base language runner.
I'm going to close this issue for now. Please feel free to re-open if you uncover some details of where this tool is mis-configured. I'm just not really able to help here unfortunately :(
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
🐛 Bug Report
I ran this command in Windows PowerShell v5.1. Here is the whole terminal text:
To Reproduce
Run the command on a Windows device that has space characters in the User folder.
Expected behavior
The command can run with special characters in the path.
Project file reproducing this issue (highly encouraged)
I think it is not necessary.
Environment
OS: Windows 11 23H2 Selenium IDE Version: 3.17.2 Selenium SIDE Runner Version: 4.0.0-alpha.61 Node version: v18.18.1 Browser Version: 119.0.6045.200 (Official Build) (64-bit)