New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: upgrade to polkadot v0.9.28 #564
Conversation
…/Basilisk-node into polkadot-v0.9.26
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.
Apart from some small details, LGTM.
It would be nice if someone else could also look at this PR before merging back to master.
|
Where did you find this line? I can't find it. XcmConfig doesn't have this field. |
From your PR description up above :-D |
Yes, you are right. I will update the description. And yes, we don't have benchmarks for it. @enthusiastmartin what to do if we want to add benchmarks for a pallet that we haven't benchmarked before? Is it enough to just add new file with the default weights to the |
let _ = <ExchangeAssetsIntentionCount<T>>::clear(u32::MAX, None); | ||
let _ = <ExchangeAssetsIntentions<T>>::clear(u32::MAX, None); |
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.
How is ExchangeAssetsIntentions
bounded?
Not the purpose of this PR, but we should know and it should be documented IMO
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.
Doesn't need to block merging this PR I guess as it's a different concern, but we should have a task tracking this IMO
// The latest versions of the orml-currencies pallet don't emit events. | ||
// The infrastructure relies on the events from this pallet, so we use the latest version of | ||
// the pallet that contains and emit events and was updated to the polkadot version we use. | ||
impl pallet_currencies::Config for Runtime { |
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.
I'm confused, I saw the events being removed from some tests, no?
orml_currencies::Event::Transferred { | ||
currency_id, | ||
from: *ALICE, | ||
to: *TREASURY, | ||
amount: 500, | ||
} | ||
.into(), |
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.
There is a comment in the runtime that orml_currencies was forked to keep these events, but they seem to be removed here?
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.
I removed orml events that followed events from the balances
or tokens
pallets. So we test that transfers are executed.
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.
Ah, so pallet_currencies
keeps some but not all events?
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.
It keeps all events, but I removed events from tests if there was an event from balances
or tokens
corresponding to the same transfer. A transfer emits two events, one from balances/tokens
and one from currencies
They need to be added in the benchmark listing in the runtime lib.rs, 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.
resolve all comments first.
Notable changes:
Rename:
Class
->Collection
,Instance
->Item
Use our own copy of
orml_currencies
pallet fromwarehouse
New benchmarking commands (
node/src/command.rs
)No need for
#[transactional]
macroImplemented migration for
pallet_nft
in warehouseImplemented migration for
pallet_marketplace
Added migration for
pallet_uniques
The version of
fixed
crate fixed to1.17.0
Use
polkadot
with patched XCM executorAdd
cumulus_pallet_xcmp_queue
to benchmarkingNew or updated runtime configuration parameters:
orml_tokens::MaxReserves = 50
orml_tokens::ReserveIdentifier = ()
pallet_currencies::CheckAssociatedRelayNumber = RelayNumberStrictlyIncreases
pallet_elections_phragmen::MaxCandidated = 1_000
pallet_elections_phragmen::MaxVoters = 10_000
pallet_uniques::CreateOrigin = NeverEnsureOrigin
pallet_uniques::Locker = ()
cumulus_pallet_xcmp_queue::WeightInfo = ()
orml_xtokens::MultiLocationsFilter = Everyting
orml_xtokens::ReserveProvider = AbsoluteReserveProvider
orml_xtokens::MinXcmFee = ParachainMinFee