Apps: Sending >1G from Charlie to Bob fails

[chevdor]

Using substrate --dev and polkadot-js-ui v0.21.0

Sending 1G works, 2G fails, another 1G works, etc...

[chevdor]

The limit seems to be 1073M
1074M fails

[jacogr]

Need to check if we are encoding it 100%

[ltfschoen]

I just tried it with the latest "next" branch polkadot-js-ui v0.21.0, and running a paritytech/substrate node with ./target/release/substrate --dev that had version substrate 0.1.0-25641b62-x86_64-macos, and i was able to send from CHARLIE to BOB the following consecutively without any errors: 1074M, then 1075M, then 1074G, then 1075G, etc. After topping Bob up with more funds Iwas also able to send 2.3P back from BOB to CHARLIE.

Are you still encountering the issue @chevdor ? If so could you please show the logs of your browser inspector

[chevdor]

Tried again using https://polkadot.js.org/apps/next/#/transfer (0.21.0) and I still see the issue.

[chevdor]

I did a refresh and opened the dev console to gather logs and in my attempts, it worked.
So there IS still something but I did not catch the logs yet. I will try again.

[chevdor]

Make sure you use MEGA as unit. I think I forgot to switch back to Mega after the refresh, explaining why my previous attempt did not fail.

and the details on the issue:

[chevdor]

For the sake of proper testing, I also tried in 'incognito' mode and the issue remains visible.
The following maybe relevant: I am using substrate 0.1.0-ec4407e3-x86_64-macos
And the accounts seem to not matter, my last test was between Alice and Bob. As long as accounts have enough funds, the issue should be visible.

[ltfschoen]

@chevdor you're using an old version of substrate. your substrate version includes the git commit hash https://github.com/paritytech/substrate/commits/ec4407e3 of the substrate repo, which is about a month old.

please try fetching the latest version of substrate and then check if you still encounter the same error. these are the steps i follow on macOS:

git clone https://github.com/paritytech/substrate;
cd substrate;
git checkout master;
git remote add upstream https://github.com/paritytech/substrate;
git pull --rebase upstream master;
curl https://sh.rustup.rs -sSf | sh;
rustup update nightly;
rustup target add wasm32-unknown-unknown --toolchain nightly;
rustup update stable;
rustup default stable;
cargo install --git https://github.com/alexcrichton/wasm-gc --force;
cargo install --git https://github.com/pepyakin/wasm-export-table.git --force;
brew install openssl; brew upgrade openssl;
brew install cmake; brew upgrade cmake;
rustc --version; cargo --version;
./scripts/build.sh;
git log --pretty=full;
cargo run -- --version;
cargo run -- --dev purge-chain;
cargo run -- --dev --telemetry --telemetry-url ws://telemetry.polkadot.io:1024

When you run git log --pretty=full;, the first eight characters of the latest commit hash (i.e. '0e852691cc28c544dd38b808db4a083870ef2a4c') should match the commit hash that's shown when you check you the substrate version with cargo run -- --version; (i.e. '0e852691 thats shown in 'substrate 0.1.0-0e852691-x86_64-macos')

[jacogr]

It 100% still exists in the current version, it is not a commit issue here at all.

(As a funny point - @chevdor actually logged the commit-hash issue as part of the version and telemetry in Substrate way-back-when, we should thank him we have it available everywhere - actually started the implementation of it as well, however he was beaten to the punch)

[ltfschoen]

i just used the latest version of substrate "master" branch substrate 0.1.0-0e852691-x86_64-macos using the latest version of the "next" branch of polkadot-js-ui v0.21.0 using the above approach, and i was able to replicate the error that @chevdor encountered when sending a transaction of 1074 MEGA or greater.

The error shown in the substrate node is shown as:

[polkadot-js-bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.