Repository navigation
create-workspace script produces rush bundle error #7108
Description
Description of the issue
I was trying to run the repo locally on my machine.
I am unable login into the ws1 workspace with user1 credentials. It gives an error "account not found" when trying to login.
It is because create-workspace command had failed
Your environment
- Version of Huly: latest
- Browser (and version): Chrome 131
- Your operating system (and version): macos 15
Steps to reproduce
- install rush and clone and cd into the repo
- sh ./scripts/presetup-rush.sh
- sh ./scripts/build.sh
- sh ./scripts/create-workspace.sh
- check the output for the errors
Expected behaviour
It should create the desired workspace and user
Actual behaviour
Upon running the rushx run-local create-workspace ws1 -w DevWorkspace command, I get the following error:
Found configuration in /Users/instinct/Desktop/huly-platform/rush.json
Rush Multi-Project Build Tool 5.134.0 - Node.js 20.5.1 (pre-LTS)
Your version of Node.js (20.5.1) is not a Long-Term Support (LTS) release. These versions frequently have bugs. Please consider installing a stable release.
> "rush bundle --to @hcengineering/tool >/dev/null && cross-env SERVER_SECRET=secret ACCOUNTS_URL=http://localhost:3000 TRANSACTOR_URL=ws://localhost:3333 MINIO_ACCESS_KEY=minioadmin MINIO_SECRET_KEY=minioadmin MINIO_ENDPOINT=localhost MONGO_URL=mongodb://localhost:27017 DB_URL=mongodb://localhost:27017 TELEGRAM_DATABASE=telegram-service ELASTIC_URL=http://localhost:9200 REKONI_URL=http://localhost:4004 MODEL_VERSION=$(node ../../common/scripts/show_version.js) GIT_REVISION=$(git describe --all --long) node --expose-gc --max-old-space-size=18000 ./bundle/bundle.js create-workspace ws1 -w DevWorkspace"
Your version of Node.js (20.5.1) is not a Long-Term Support (LTS) release. These versions frequently have bugs. Please consider installing a stable release.
Your version of Node.js (20.5.1) is not a Long-Term Support (LTS) release. These versions frequently have bugs. Please consider installing a stable release.
"@hcengineering/model-all (bundle)" completed with warnings in 1.21 seconds.
Your version of Node.js (20.5.1) is not a Long-Term Support (LTS) release. These versions frequently have bugs. Please consider installing a stable release.
"@hcengineering/tool (bundle)" completed with warnings in 1.14 seconds.
Operations succeeded with warnings.
Error: Failed calling rush bundle --to @hcengineering/tool >/dev/null && cross-env SERVER_SECRET=secret ACCOUNTS_URL=http://localhost:3000 TRANSACTOR_URL=ws://localhost:3333 MINIO_ACCESS_KEY=minioadmin MINIO_SECRET_KEY=minioadmin MINIO_ENDPOINT=localhost MONGO_URL=mongodb://localhost:27017 DB_URL=mongodb://localhost:27017 TELEGRAM_DATABASE=telegram-service ELASTIC_URL=http://localhost:9200 REKONI_URL=http://localhost:4004 MODEL_VERSION=$(node ../../common/scripts/show_version.js) GIT_REVISION=$(git describe --all --long) node --expose-gc --max-old-space-size=18000 ./bundle/bundle.js create-workspace ws1 -w DevWorkspace. Exit code: 1
Possible solutions
(Not obligatory)
If you know how to fix the bug, please describe your solution here.
Activity
haiodo commentedon Nov 5, 2024
Hi @uinstinct it is because of Node version, our scripts are not expect to have any extra output, could you please try update to more fresh version. We use v20.13.
uinstinct commentedon Nov 6, 2024
Thanks @haiodo! That worked!
There is a problem with create-workspace script which seems to hang after running. (I restarted from the presetup-rush script)
Diving deeper, I found the reason was the
rushx run-local configure ws1 --list --enable '*'command which is actually hanging.Here is the output I am seeing:
Any thoughts what the problem could be?
MichaelUray commentedon Oct 20, 2026
The create-workspace script referenced here has since been removed from the repository, so the reported failure no longer applies to the current setup. If maintainers agree, please consider closing.
MichaelUray commentedon Oct 20, 2026
@uinstinct — as explained above, this does not look like something that can be addressed in the codebase. Could you please close this issue if you agree? If you think there is a code change needed after all, please describe what should change.