Conversation
…ytech/polkadot into prgn-remove-old-service-second-try * 'prgn-remove-old-service-second-try' of github.com:paritytech/polkadot: rename polkadot-service-new -> polkadot-service
* master: Update to substrate 2.0 (#1744) Companion: Handle construct_runtime breaking change. (#1692) Companion for `ModuleToIndex` to `PalletInfo` rename (#1743) Companion for substrate/pull/7161 (#1739) Companion for 7155 (WeightInfo for Babe and Grandpa) (#1736) Companion PR for #7136 (WeightInfo for Session / Offences) (#1735)
bkchr
left a comment
There was a problem hiding this comment.
Besides my comments, I think it is okay.
A general note, the old service file should have been copied to the node/service directory and the 3 changes related to the new architecture should have been applied. Now it was much more complicated to review this, to make sure nothing was forgotten.
| /// This is an advanced feature and not recommended for general use. Generally, `build_full` is | ||
| /// a better choice. | ||
| #[cfg(feature = "full-node")] | ||
| pub fn new_full<RuntimeApi, Executor>( |
There was a problem hiding this comment.
In the old service this also got a parameter "test" which was forgotten here.
There was a problem hiding this comment.
Maybe we can ignore it, I'm not sure. I don't have implemented this.
@cecton was this AFAIK.
There was a problem hiding this comment.
It's because the test service uses the test runtime and don't need prometheus.
But for the second place with kusama hard forks I think the condition !test can safely be removed because the test config.chain_spec.is_kusama() will be false for the test runtime anyway.
Originally there was one important other thing: the ValidationPool is built differently for the test node: https://github.com/paritytech/polkadot/blob/rococo-branch/service/src/lib.rs#L414
There was a problem hiding this comment.
It's because the test service uses the test runtime and don't need prometheus.
but if prometheus_config.is_none(), this line will not be executed anyway, so it seems redundant
Originally there was one important other thing: the ValidationPool is built differently for the test node: https://github.com/paritytech/polkadot/blob/rococo-branch/service/src/lib.rs#L414
do you think it's worth adding back to master or it can be taken care of in the rococo-branch?
There was a problem hiding this comment.
do you think it's worth adding back to master or it can be taken care of in the rococo-branch?
I'm pretty sure rococo-branch is temporary (@bkchr correct me if I'm wrong). We will need to get it back or add a feature of some sort.
but if prometheus_config.is_none(), this line will not be executed anyway, so it seems redundant
You're right!! I think it's because new_full used to be a macro so the code was compiled on cumulus where we don't have the dependency for that. Now it's not an issue anymore. 🎉
🤔 comes to think of it... it was the same thing for the kusama forks thingy.
Cool!! We can drop this safely
Yes, it was tested on a sentry node, also sentry and validator on kusama. Thanks for the review, I'll apply the changes while Peter is out. |
|
It should also be tested on a Polkadot validator. |
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
* master: provisioner tests: remove tokio from dev-dependencies (#1745)
bkchr
left a comment
There was a problem hiding this comment.
After it is tested on a Polkadot validator, it should be fine to merge.
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
|
Burnin on a Polkadot validator has been running for four days now, and it seems to be operating normally. |
|
bot merge |
|
Trying merge. |
This reverts commit 42fbca6.
* master: Collator protocol followup (#1741) Revert "Remove Old Service, 2nd try (#1732)" (#1758) Remove Old Service, 2nd try (#1732) collation-generation: guide and tidying (#1753) Companion for #7111 (Introduce `cancel_proposal` and `blacklist`) (#1728) Parachains: Introduce a dummy module to include the Origin. (#1749) provisioner tests: remove tokio from dev-dependencies (#1745)
i.e. Revert "Revert "Remove Old Service, 2nd try (#1732)" (#1758)" This reverts commit c80f7b6. Closes #1757. We now have some evidence that the polkadot validator was producing blocks after all; the reason the blocks_constructed metric was 0 was that as a new metric it hadn't yet been incorporated into that branch's codebase. See #1757 (comment) As this PR is based on a newer `master` branch than the previous one, that should hopefully no longer be an issue.
* Remove old service, 3rd try i.e. Revert "Revert "Remove Old Service, 2nd try (#1732)" (#1758)" This reverts commit c80f7b6. Closes #1757. We now have some evidence that the polkadot validator was producing blocks after all; the reason the blocks_constructed metric was 0 was that as a new metric it hadn't yet been incorporated into that branch's codebase. See #1757 (comment) As this PR is based on a newer `master` branch than the previous one, that should hopefully no longer be an issue. * paras trait now has an Origin type * initial work running a two node local net * use the right incantations so the nodes produce blocks together * improve internal documentation Co-authored-by: Bastian Köcher <git@kchr.de>
#1630 was immediately reverted in #1731 due to insufficient testing. This PR contains the same changeset from #1630 in a form which can be merged after future testing.