-
In the older runtime recipes that I deleted in 1495d8616b40, There was a section called "Print a message" which showed how to output simple debugging logs. That is not in the new https://substrate.dev…
-
Sometimes, our parachain node gets stucks at some block.
Parachain, related blocks looks like this:
```
2023-08-23 12:35:15.944 INFO tokio-runtime-worker substrate: [Parachain] ⚙️ Preparing …
-
We had a spike of 1k warning messages from a single peer on Kusama:
https://grafana.teleport.parity.io/goto/Vs5GETjIR?orgId=1
```
WARN tokio-runtime-worker peerset: Report 12D3KooWJPXURGJ1nMa3FwA8a…
-
After doing a purge of the network, one of our bootnode got stuck at a given block height. Even after restarting it gets stuck.
Something weird from the log is the fact it imported blocks in the reve…
-
This roadmap deals with the development of Emergence core modules. This roadmap is not final, subject to edits and change. I encourage all to expand subcomponents and write down more details developme…
-
For newer runtimes, the runtime version can now be obtained from the WASM custom sections from the wasm code, and there is no longer a need to instantiate the full runtime to check its version.
For…
qdm12 updated
7 months ago
-
This is an involved issue. Before any implementation is started, please discuss the design of the CLI API here.
To facilitate testing and development, it would be convenient to have the ability to …
-
**Describe the bug**
Every time I run the local development network, the block stop at #199. No new blocks are mined after and every transaction that I try to do when this happens raises the followin…
-
Since Aug 04 21:33:00 block #4,522,480 node doesn't produce any blocks, error:
```
Thread 'tokio-runtime-worker' panicked at 'Could not lookup information required to validate the transaction', /h…
-
**rust-analyzer version**: (eg. output of "rust-analyzer: Show RA Version" command, accessible in VSCode via Ctrl/⌘+Shift+P)
```
rust-analyzer version: 0.3.2053-standalone (fd74511f3 2024-07-2…