You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I upload a packaging file in Windows, ProcessBuilder cannot find the file.
To Reproduce
1.Project List-> Packaging column
2. Upload OSS Package
Expected behavior
a file is uploaded normally.
Screenshots
System Environment (please complete the following information):
Browser : chrome
os : windows
Additional context
I looked up the problem and found that /bin/bash doesn't exist on Windows.
I try replaced /bin/bash with cmd.exe, and replacing the switch -c with /c.
However, modifications do not solve the problem.
The text was updated successfully, but these errors were encountered:
The shellCommand is called as Runtime.getRuntime().exec, so it should be executed regardless of OS. So even if you change it to cmd.exe, the error may have occurred.
I am wondering how to fix it.
Should I guide bash with pre-installation on windows....🤔
I'll check it carefully.
thanks for commenting the error.
JoHyoju04
changed the title
When I upload a packing file in Windows, ProcessBuilder cannot find the file.
When I upload a packaging file in Windows, ProcessBuilder cannot find the file.
Oct 13, 2021
Describe the bug
When I upload a packaging file in Windows, ProcessBuilder cannot find the file.
To Reproduce
1.Project List-> Packaging column
2. Upload OSS Package
Expected behavior
a file is uploaded normally.
Screenshots
![image](https://user-images.githubusercontent.com/47858282/131506708-6b048b99-ce47-49a0-add7-c9025f027caa.png)
![image](https://user-images.githubusercontent.com/47858282/131506903-181fb17c-36a6-4bec-be10-381bd8157e34.png)
System Environment (please complete the following information):
Additional context
I looked up the problem and found that /bin/bash doesn't exist on Windows.
I try replaced /bin/bash with cmd.exe, and replacing the switch -c with /c.
However, modifications do not solve the problem.
The text was updated successfully, but these errors were encountered: