Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.3.4f1
Issue ID
780150
Regression
No
[OSX] Cache Server won't start if there are spaces in the --path argument
Reproduction steps:
1) Create a directory with spaces in it
2) Run RunOSX.command command like this"
exec /path/to/RunOSX.command --nolegacy --path "/path/with/some\ spaces/Cache5.0/" &
--- You will get an error like this:
Unknown option: spaces/Cache5.0/
Usage: node main.js --port serverPort] [--path pathToCache] [--legacypath pathToCache] [--size maximumSizeOfCache] [--nolegacy] [--verify
--port: specify the server port, only apply to new cache server, default is 8126
--path: specify the path of the cache directory, only apply to new cache server, default is ./cache5.0
--legacypath: specify the path of the cache directory, only apply to legacy cache server, default is ./cache
--size: specify the maximum allowed size of the LRU cache for both servers. Files that have not been used recently will automatically be discarded when the cache size is exceeded
--nolegacy: do not start legacy cache server, otherwise legacy cache server will start on port 8125.
--verify: verify the Cache Server integrity, no fix.
--fix: fix the Cache Server integrity.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
Add comment