-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
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
README setup instructions not working on Ubuntu #2414
Comments
On the machine where I did get yarn setup to work, here is the error encountered when running
...
[DATA] #62 [dashmate_helper build-js 3/5] RUN --mount=type=cache,sharing=shared,id=cargo_registry_index,target=/root/.cargo/registry/index --mount=type=cache,sharing=shared,id=cargo_registry_cache,target=/root/.cargo/registry/cache --mount=type=cache,sharing=shared,id=cargo_git,target=/root/.cargo/git/db --mount=type=secret,id=AWS source /root/env && cargo chef cook --recipe-path recipe.json --profile "dev" --package wasm-dpp --target wasm32-unknown-unknown --locked && if [[ -x /usr/bin/sccache ]]; then sccache --show-stats; fi UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "#". |
On the machine where EDIT: tracked this back further and the error happens due to this line being set to true (https://github.com/dashpay/platform/blob/v1.7.1/scripts/configure_dashmate.sh#L18): Looks like that value then links to this file which contains the unset vars mentioned in the error message: https://github.com/dashpay/platform/blob/v1.7.1/packages/dashmate/docker-compose.build.dashmate_helper.yml This is the error:
|
And here is how I set up the VM: sudo apt install -y build-essential libssl-dev pkg-config clang cmake llvm unzip jq
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.1/install.sh | bash
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion" # This loads nvm bash_completion
nvm
nvm install 20
node --version
for pkg in docker.io docker-doc docker-compose docker-compose-v2 podman-docker containerd runc; do sudo apt-get remove $pkg; done
# Add Docker's official GPG key:
sudo apt-get update
sudo apt-get install ca-certificates curl
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc
# Add the repository to Apt sources:
echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \
$(. /etc/os-release && echo "$VERSION_CODENAME") stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt-get update
sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
sudo usermod -aG docker $USER
exit
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
exit
rustc --version
wget https://github.com/protocolbuffers/protobuf/releases/download/v27.3/protoc-27.3-linux-x86_64.zip
sudo unzip protoc-*-linux-x86_64.zip -d /usr/local
protoc --version
cargo install [email protected]
git clone https://github.com/dashpay/platform.git
cd platform/
corepack enable
yarn --version
yarn setup
yarn start |
Expected Behavior
Following the install instructions in the README results in a working environment where
yarn setup
andyarn start
work.Current Behavior
Numerous issues encountered including confusion over what version of wasm-bindgen-cli should be installed. The README says 0.2.86; however, on one machine (clean Ubuntu 22.04 VM), it won't build without using 0.2.99.
Possible Solution
Steps to Reproduce (for bugs)
yarn setup
and/oryarn start
Context
Your Environment
The text was updated successfully, but these errors were encountered: