substrate

A user complained that the suggestions under the recovery field where not big enough.
I saw many users just ignore these words

Quote from one of thoses

I hadn't seen them

Motivation

It’s good to support as many local languages as it possible. One of steps of it is creating easy method to support multiple languages in docs. Currently documentation located in staketechnologies/plasmdocs repo.

Results

Result for closing this is PR into staketechnologies/plasmdocs repo with implementation multi language feature for gitbook generator and moving

Started to see this after recent upgrade:

t=2020-12-29T19:45:41+0000 lvl=info msg="Starting ChainBridge..."
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x633d16]

goroutine 1 [running]:
math/big.(*Int).Cmp(0x0, 0xc0000a1880, 0x0)
        /usr/local/go/src/math/big/int.go:326 +0x26
github.com/Chain

When sending multiple requests, the data log causes an problem incorrect nonce:

Error: Input("Rpc error: Server responded to our request with an error: Error { code: ServerError(1014), message: \"Priority is too low: (140000000 vs 140000000)\", data: Some(String(\"The transaction has too low priority to replace another transaction already in the pool.\")) }")
`Error: Input("Rpc error: Server

This would be good to inform users which runtimes will actually emit traces vs which will not. It would also be a good debugging tool in case a user is confused as to why there are traces missing for some runtime

Patch release, should be trivial
Will need to follow the same flow as normal - see #65 for a checklist 🙏🏼