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
Every message directed to the user must go though a common interface that is thread-safe. There should be no interleaving of messages caused by parallelization.
Aimee has previously installed dfx. Today when she ran dfx new firsttest to create a Dfinity project, she had a confusing experience.
This is what she saw:
$ dfx new firsttest
The Dfinity Canister SDK sends anonymous usage data to Dfinity Stiftung by
default. If you wish to disable this behavior, then please set the environment
variable DFX_TELEMETRY_DISABLED=1. Learn more at https://sdk.dfinity.org.
Fetching manifest https://sdk.dfinity.org/manifest.json
⠋ Checking for latest dfx version...
You seem to be running an outdated version of dfx.
You are strongly encouraged to upgrade by running 'dfx upgrade'!
Version v0.6.20 installed successfully.
Creating new project "firsttest"...
CREATE firsttest/src/firsttest_assets/assets/sample-asset.txt (24B)...
CREATE firsttest/src/firsttest/main.mo (107B)...
CREATE firsttest/dfx.json (484B)...
CREATE firsttest/.gitignore (165B)...
⠐ Checking for latest dfx version...
CREATE firsttest/src/firsttest_assets/public/index.js (149B)...
CREATE firsttest/package.json (288B)...
CREATE firsttest/webpack.config.js (2.15KB)...
⠉ Checking for latest dfx version...
⠒ Checking for latest dfx version...
⠠ Installing node dependencies...
⠤ Checking for latest dfx version...
⠖ Installing node dependencies...
> [email protected] install /Users/aimeez/github/dfinity-project/firsttest/node_modules/watchpack-chokidar2/node_modules/fsevents
> node install.js
⠤ Checking for latest dfx version...
⠖ Checking for latest dfx version...
⠒ Checking for latest dfx version...
⠁ Checking for latest dfx version...
npm WARN [email protected] No repository field.
npm WARN [email protected] No license field.
⠙ Checking for latest dfx version...
13 packages are looking for funding
run `npm fund` for details
found 1 high severity vulnerability
⠒ Checking for latest dfx version...
⠂ Checking for latest dfx version...
===============================================================================
Welcome to the internet computer developer community!
You're using dfx 0.6.20
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▄▄▄▄▄▄▄▄▄▄▀▀▀▀▀▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄▀▀▀▀▀▀▄▄▄▄▄▄▄▄▄▄
▄▄▄▄▄▄▄▄▀ ▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀ ▀▄▄▄▄▄▄▄▄▄
▄▄▄▄▄▄▄▄▀ ▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀ ▄▄▄▄▄▄▄▄
▄▄▄▄▄▄▄▄ ▀▄▄▄▄▄▄▄▄▄▄▄▄▀ ▄▄▄▄▄▄▄
▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄
▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄
▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▀
▀▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄▀ ▀▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄
▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀ ▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀
▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀ ▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀▀ ▀▀▄▄▄▄▄▄▄▄▄▄▄▄▄▄▀
▀▀▀▀▀▀▀▀▀▀▀ ▀▀▀▀▀▀▀▀▀▀▀
To learn more before you start coding, see the documentation available online:
- Quick Start: https://sdk.dfinity.org/docs/quickstart/quickstart-intro.html
- SDK Developer Tools: https://sdk.dfinity.org/docs/developers-guide/sdk-guide.html
- Motoko Language Guide: https://sdk.dfinity.org/docs/language-guide/motoko.html
- Motoko Quick Reference: https://sdk.dfinity.org/docs/language-guide/language-manual.html
If you want to work on programs right away, try the following commands to get started:
cd firsttest
dfx help
dfx new --help
===============================================================================
The dfx version check is happening in parallel to the creation and build of the “firsttest” project, causing a confusing interleaving of messages.
The text was updated successfully, but these errors were encountered:
I could not reproduce the behavior. I manually installed dfx 0.6.1 and also created a new project. I didn't see any Checking for latest dfx version... message.
While it IS confusing that the following two lines showed together:
You are strongly encouraged to upgrade by running 'dfx upgrade'!
Version v0.6.20 installed successfully.
For newbies who are not familiar with the dfx cache mechanism. They may take it as: it suggest an upgrade and installed it without my approval. What actually happened was that the user installed dfx when the version was 0.6.20 and when she ran dfx new for the first time, the lastest version has already been 0.6.21. And separately the 0.6.20 sdk cache is missing, so it has to be installed.
I would suggest to improve the console output by:
Tell the user both the current version and the latest version as:
You seem to be running an outdated version of dfx (current 0.6.20 -> latest 0.6.21).
Make it more clear on installing current version which missing cache:
Missing cache for current version v0.6.20
Installing version v0.6.20
Version v0.6.20 installed successfully
P.S. It's good to have one unified dfx (for rust, we have rustup, cargo, rustc). While we should also make it clear about what could be expected from dfx.
Every message directed to the user must go though a common interface that is thread-safe. There should be no interleaving of messages caused by parallelization.
The text was updated successfully, but these errors were encountered: