-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Conversation
I'd prefer to not go for this solution of "un-linking" the dead links. The problem is that the documentation is outdated. Doc-links can detect when the documentation is outdated. If you disable the doc-links, it doesn't solve the problem of the documentation being outdated. You're just killing the messenger. |
@@ -1404,7 +1404,6 @@ impl_runtime_apis! { | |||
#[cfg(feature = "try-runtime")] | |||
impl frame_try_runtime::TryRuntime<Block> for Runtime { | |||
fn on_runtime_upgrade() -> Result<(Weight, Weight), sp_runtime::RuntimeString> { | |||
frame_support::debug::RuntimeLogger::init(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the compilation is failing because debug doesn't exist anymore cc @kianenigma
I think logger is automatically initialized now, so we can remove no ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah this should be removed, and I think there might be other places in try-runtime
that we use this the deprecated logger as well.
I've made an issue here: https://github.com/paritytech/ci_cd/issues/103, I hope we have this in the CI soon.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unless this is urgent, please either do all the appropriate changes in sc-network
or (more likely) revert so that I do it later.
@@ -65,7 +65,7 @@ | |||
//! origin can not bail out in any way, if their solution is queued. | |||
//! | |||
//! Upon the end of the signed phase, the solutions are examined from best to worse (i.e. `pop()`ed | |||
//! until drained). Each solution undergoes an expensive [`Pallet::feasibility_check`], which | |||
//! until drained). Each solution undergoes an expensive `Pallet::feasibility_check`, which |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is private item
yes, sorry done |
If there are further doc-related issues, I'd be happy of the fixes that are related to |
This PR was more a draft for the stuff needed to change, if you need the try-runtime changes feel free to take them. Sorry if it felt pushing, I'm also not entirely convinced if it is the good way of addressing try-runtime issue. |
bot merge |
Checks failed; merge aborted. |
this fixes the cmd:
RUSTDOCFLAGS="-Dwarnings" time cargo +nightly doc --no-deps --workspace --all-features
Some outdated doc in network + link to private itemSome doc in sc_network were outdated, and some were linking to private item. I'm not sure how to solve them so I just remove the invalid link. But some are still outdated. (maybe cc @tomaka )Issue with feature try-runtime
The feature try-runtime is breaking the build for unknown reason: (to reproduce go to the first commit 16b38eb and execute the cmd:
RUSTDOCFLAGS="-Dwarnings" time cargo +nightly doc --no-deps --workspace --all-features
)Thus I actually implemented in the trait
OnRuntimeUpgrade
the default implementation forpre_upgrade
andpost_upgrade
. The disadvantage is that if node-runtime forget to boundmy-pallet/try-runtime
in its Cargo.toml then the pallet implementation will simply be ignored.