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
The former does nothing particular, but it adds a few extra runtime apis that can be used to test the runtime with a tool in the try-runtime family.
The latter will impact the wasm blob and enable all the runtime logging. This will slightly reduce performance.
These wasm blobs will then allow 3rd party teams, including Parity to run better monitoring nodes.
If done by someone familiar with the fellowship CI/release, I'd be happy to complement this work by providing a detailed guide on how to use these blobs to do better monitoring with these notes.
@liamaharon you might know any prior attempt at this, if any?
The text was updated successfully, but these errors were encountered:
This will be very useful to debug chains with Chopsticks. I had multiple occurrences that I need to make such debug build to figure out why some XCM fails on relaychain/system parachain.
This is a request to publish each runtime with two properties:
--features try-runtime
--features on-chain-release-build
:runtimes/.github/workflows/release.yml
Line 59 in 40f849d
The former does nothing particular, but it adds a few extra runtime apis that can be used to test the runtime with a tool in the try-runtime family.
The latter will impact the wasm blob and enable all the runtime logging. This will slightly reduce performance.
These wasm blobs will then allow 3rd party teams, including Parity to run better monitoring nodes.
If done by someone familiar with the fellowship CI/release, I'd be happy to complement this work by providing a detailed guide on how to use these blobs to do better monitoring with these notes.
@liamaharon you might know any prior attempt at this, if any?
The text was updated successfully, but these errors were encountered: