Walkthrough and edit - please claim in title or issue body.

As is our first use of dfinity and motoko I need to use it as microservice with my own backend so it'll be storage for the sensitive data.

I Searched the whole internet on how can I send request to motoko project but I didn't find anything helpful.

Is your feature request related to a problem? Please describe.
New features are being added to the NNS UI application and we want to at least provide basic task information in the Quick start so that users don't have to hunt down random Medium articles or blog posts that are light on instructions or out-of-date.

• dfx canister create --with-cycles
• dfx deploy --with-cycles

There's some information in the release notes that could serve as the basis for adding this option to the CLI reference:
https://sdk.dfinity.org/docs/release-notes/0.6.24-rn.html

Describe the bug
This bug report will detail issues found in the Incrementing a counter Rust tutorial

** To Reproduce **

1. Add a open curly bracket in the dfx.json code block to match the close curly brace:

"build": "cargo build --target wasm32-unknown-unknown --package  rust_counter --release",
"candid": "src/rust_counter/counter.did",
"wasm": "target/wasm32-unknown-unknown/release/rust_counter.wasm",
"type": "custom"
}

Should be:

"rust_counter": {
      "build": "cargo build --target wasm32-unknown-unknown --package  rust_counter --release",
      "candid": "src/rust_counter/counter.did",
      "wasm": "target/wasm32-unknown-unknown/release/rust_counter.wasm",
      "type": "custom"
    }

2. Step #4 doesn't have a copy widget on the code block
3. Version bump the second Cargo.toml (within the src directory). Was:

[package]
name = "rust_counter"
version = "0.1.0"
authors = ["DFINITY <[email protected]>"]
edition = "2018"

[lib]
path = "counter.rs"
crate-type = ["cdylib"]

[dependencies]
ic-cdk = { path = "../../../cdk-rs/src/ic-cdk", version = "0.1.0" }
ic-cdk-macros = { path = "../../../cdk-rs/src/ic-cdk-macros", version = "0.1.0" }
ic-types = "0.1.1"
lazy_static = "1.4.0"

should be

[package]
name = "rust_counter"
version = "0.1.0"
authors = ["DFINITY <[email protected]>"]
edition = "2018"

[lib]
path = "counter.rs"
crate-type = ["cdylib"]

[dependencies]
ic-cdk = { path = "../../../cdk-rs/src/ic-cdk", version = "0.2.4" }
ic-cdk-macros = { path = "../../../cdk-rs/src/ic-cdk-macros", version = "0.2.4" }
ic-types = "0.1.1"
lazy_static = "1.4.0"

The official access control tutorial is failing due to the latest changes in the SDK. Create new identities returns their wallet canister id not the identity principal.

Walkthrough and edit

Describe the bug
The docs specify the wrong upper limit of the --memory-allocation flag.

To Reproduce
Steps to reproduce the behavior:

Run the code:
dfx canister --network=ic install --all --memory-allocation=16GB --mode=upgrade

Receive the error:
The Replica returned an error: code 5, message: "Canister moi4t-aqaaa-aaaaa-qbbra-cai trapped explicitly: An error happened during the call: 5: MemoryAllocation expected to be in the range [0..8589934592], got 16000000000"`

The docs say:

--memory-allocation <memory-allocation> Specifies how much memory the canister is allowed to use in total. You can set this value in the range of 0 to 256 TB. The default is 8GB.

Expected behavior
The docs should specify the actual ceiling limit for canister memory, not 256 TB.

The CLI should reflect what the ceiling is in the docs.

Additional context
Forum thread here

I cant seem to find the place to ask this question. I am unable to make a comment in the forum for some reason.
In the docs at #_revise_the_source_code_in_your_program

After changing the code, building and reinstalling I get this type error:

~/Downloads/MOKOTO/location_hello master*
❯ dfx build && dfx canister install favorite_cities -m reinstall
Building canisters...
Installing code for canister favorite_cities, with canister_id cxeji-wacaa-aaaaa-aaaaa-aaaaa-aaaaa-aaaaa-q

~/Downloads/MOKOTO/location_hello master*
❯ dfx canister call favorite_cities location '(vec {"San Francisco";"Paris";"Rome"})'

main.mo

actor {
    public func location(cities : [Text]) : async Text {
        return "Hello, from " # (debug_show cities) # "!";
    };
    public func location_pretty(cities : [Text]) : async Text {
        var str = "Hello from ";
        for (city in cities.vals()) {
                str := str # city #", ";
        };
        return str # "bon voyage!";
    }
};

Also, do I have to rebuild everytime I make a change?

Thank you.

Disregard. I had to change directories and fix the path in dfx.json.

Thank you. Please do tell where I should be posting this and all about rebuilding. Thank you.

Describe the command or option

• dfx start --emulator

Add a usage scenario and example**

Walkthrough and edit

From JIRA:

• Fix Quick start links.
• Fix Download page to include instructions / hide future options
• Change tile headings and descriptions
• Fix language guide links.

We are starting to collect a pretty big backlog of changes related to the 0.7.0-beta releases. It seems like a good idea to do a "catch-up package" of release notes that we can add to for the launch of 0.7.0 (public "latest").

How can we obtain Neuron Identifiers when using "Claim in two steps" ?

Is there a dfx canister call to obtains Neuron Identifiers list ?

https://github.com/dfinity/docs/blob/master/modules/token-holders/pages/seed-donations.adoc#claim-in-two-steps

Describe the command or option

• dfx canister sign
• dfx canister send

There's some information about this here:
#368

Add a usage scenario and example**

Walkthrough and edit - This one is fine

Walkthrough and edit

From Tungsten Hackathon:

"Broken links to “Result” , “Option” and “error-types” from this page
https://sdk.dfinity.org/docs/language-guide/errors-and-options.html"

Describe the bug
The Edit button on each docs page doesn't work as it links to the /master/ branch instead of /main/.

For example, on the getting-started page, it links to

https://github.com/dfinity/docs/edit/master/modules/quickstart/pages/quickstart-intro.adoc

but should link to

https://github.com/dfinity/docs/edit/main/modules/quickstart/pages/quickstart-intro.adoc

To Reproduce
Steps to reproduce the behavior:

1. Visit any documentation page.
2. Press the "edit this page" button
3. View the 404 error on GitHub.

Expected behavior

1. Visit any documentation page
2. Click the "edit this page button"
3. Get taken to the edit view on GitHub for that page.

Screenshots

Desktop (please complete the following information):
N/A

Smartphone (please complete the following information):
N/A

Additional context
I think this can be fixed by changing master to main in the antora.ymlfile, but I was unable to build the docs locally to verify this. The contributing page mentions a page called antora-playbook.yml "in another repository" but doesn't say which. The SDK repository references https://github.com/dfinity-lab/dfinity-docs-playbook but that does not exist (or is private).

From Zendesk:

1. Using an actor in the Hello, World! program
   Capital D in Debug created an error. (Resolved when changed to lowercase)
   2: Page: Importing standard library functions
   Capital L and A in List & AssocList created an error (Resolved when changed to lowercase)

From Tungsten Hackathon:

Non-existing (or hard-to-find?) examples of variant types as enums at https://sdk.dfinity.org/docs/language-guide/motoko.html,

JSON format for IDL types, including variant and option, were not documented. This is somewhat essential information. :-)

Walkthrough and edit

Taking this one.

Walkthrough and edit - please claim in title or issue body.

The Installation through the quickstart guide (https://sdk.dfinity.org/docs/quickstart/quickstart.html) fails for me.

To make it reproducible here is a Dockerfile that triggers the issue.

FROM ubuntu:18.04
RUN apt update && apt install -y sudo curl
RUN curl -sL https://deb.nodesource.com/setup_10.x | bash - 
RUN apt install -y nodejs
RUN echo y | sh -ci "$(curl -fsSL https://sdk.dfinity.org/install.sh)"
RUN dfx --version

Simply, docker build . to witness the error.
The installation script says:

Version found: 0.5.4
Creating uninstall script in ~/.cache/dfinity
uninstall path=/root/.cache/dfinity/uninstall.sh
Checking for latest release...
tar: This does not look like a tar archive

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Will install in: /usr/local/bin
Installed /usr/local/bin/dfx

And dfx --version has no output.

Walkthrough and edit

Walkthrough and edit

I followed the quickstart guide (https://sdk.dfinity.org/docs/quickstart/quickstart.html). When starting dfx I get the following error.

> dfx start --background
⠁ Starting up the client...
Apr 02 16:12:46.759 INFO Dfinity Replica Started
Apr 02 16:12:46.759 INFO Existing node ID: 15441190334538835598
thread 'main' panicked at 'Could not rename temporary file for port report: Os { code: 18, kind: Other, message: "Invalid cross-device link" }', src/libcore/result.rs:1165:5
⠠ Replica exited with exit code: 101

Describe the command or option

Add a usage scenario and example**

We've had a note that this wasn't supported that can be removed for 0.7.0.

This limitation is no longer valid in 0.7.0-beta.1 and beyond.
-[ ] Customize the front-end #401
-[ ] Add a stylesheet #402

Describe the bug
This bug report will detail issues found in the Hello, World! Rust CDK Quick Start

To Reproduce

1. ls -l cdk_rs/src returns ls: cdk_rs/src: No such file or directory ; instead it should be ls -l cdk-rs/src which the expected. ✅
2. To modify the Cargo.toml configuration file should say To modify (or create) the Cargo.toml configuration file since folks using Dfx will need to create one ✅

3. Use the [workspace] key to specify the source file directories for your program.
   [workspace] should be a code block (since previous keys were in code blocks): [workspace] ✅

4. Version bump the second Cargo.toml (within the src directory). Was:

[package]
name = "rust_hello"
version = "0.1.0"
authors = ["Your Name <[email protected]>"]
edition = "2018"

[lib]
path = "main.rs"
crate-type = ["cdylib"]

[dependencies]
ic-cdk = { path = "../../../cdk-rs/src/ic-cdk", version = "0.1.0" }
ic-cdk-macros = { path = "../../../cdk-rs/src/ic-cdk-macros", version = "0.1.0" }

should be:

[package]
name = "rust_hello"
version = "0.1.0"
authors = ["Your Name <[email protected]>"]
edition = "2018"

[lib]
path = "main.rs"
crate-type = ["cdylib"]

[dependencies]
ic-cdk = { path = "../../../cdk-rs/src/ic-cdk", version = "0.2.4" }
ic-cdk-macros = { path = "../../../cdk-rs/src/ic-cdk-macros", version = "0.2.4" }

New Additions

1. Users need to install the ic-cdk-optimizer in order to ensure that their rust code is sufficiently small for uploading as a canister: cargo install ic-cdk-optimizer
2. Users need to make a release directory within their rust_hello directory: mkdir -p target/wasm32-unknown-unknown/release/
3. Users need to optimize their code. From the rust_hello directory: ic-cdk-optimizer target/wasm32-unknown-unknown/debug/rust_hello.wasm -o target/wasm32-unknown-unknown/release/rust_hello-opt.wasm
4. Users need to update their dfx.json to point to the optimized wasm in the canisters.rust_hello.wasm key: "wasm": "target/wasm32-unknown-unknown/release/rust_hello-opt.wasm"

From Tungsten Hackathon:

"dfx start" fails with this error:"Internet Computer replica started... \n thread 'main' panicked at 'State at height 86987 had disappeared before we had a chance to make a CUP. This should not happen.', consensus/src/catchup_package_maker.rs:111:17 \n Replica exited with signal: 6" The command "dfx start --clean" fixes it. maybe we should suggest that instead.

Walkthrough and edit

Describe the command or option

• dfx identity import

I made a rough start on this:
#387
https://sdk.dfinity.org/docs/release-notes/0.6.25-rn.html

and there's also information about using this command here:
#368

Add a usage scenario and example

Reported from Zendesk:

In the subsection "The Array module," the link to "additional array operations" leads to nowhere.

https://sdk.dfinity.org/docs/language-guide/mutable-state.html#stdlib-array

https://sdk.dfinity.org/docs/base-libraries/array#flatten

I believe the method signature should be
func flatten<A>(xs : [[A]]) : [A]

If i scroll down all the way on the Principals and caller identification page at https://sdk.dfinity.org/docs/language-guide/caller-id.html and follow the Principal link in "More operations on principals are available in Principal base library." it takes me to https://sdk.dfinity.org/docs/base-libraries/result instead of what was probably the intended page eg https://sdk.dfinity.org/docs/base-libraries/principal

Documentation

CLI reference and task updates

• dfx canister delete
• dfx canister start
• dfx canister status
• dfx canister stop

Walkthrough and edit

Describe the command or option

• dfx canister --no-wallet

Add a usage scenario and example**

The tutorial named Explore the default project says that there will be a "src" folder in explore_hello_assets with two files. When I generate a new project with dfx new , the folder is named "public" instead and does not contain any HTML, only this index.js

import explore_hello from 'ic:canisters/explore_hello';

explore_hello.greet(window.prompt("Enter your name:")).then(greeting => {
  window.alert(greeting);
});

Using dfx 0.6.26.

Describe the command or option

• dfx identity deploy-wallet

This one is a little hairy to talk about, but you can find an introduction here: https://sdk.dfinity.org/docs/release-notes/0.6.24-rn.html

Add a usage scenario and example