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
Release v0.10.34 #1573
Release v0.10.34 #1573
Conversation
/benchmark centrifuge |
✅ Uploaded benchmarks for: |
/benchmark centrifuge |
✅ Uploaded benchmarks for: |
FYI: Need to benchmark again, because the benchmarks were missing #1465 which introduced a breaking weights change. Moreover, the Centrifuge runtime did not have |
@@ -38,7 +39,7 @@ libs/traits/src/changes.rs @lemunozm | |||
libs/traits/src/data.rs @lemunozm | |||
|
|||
## Changes to runtime | |||
runtime/common/* @mustermeiszer @NunoAlexandre @hieronx @lemunozm | |||
runtime/common/* @mustermeiszer @NunoAlexandre @hieronx @lemunozm @wischli |
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 hope it's fine I have added myself here.
let n in 2..Helper::<T>::max_active_loans() - 2; | ||
|
||
let any = account("any", 0, 0); | ||
let pool_id = Helper::<T>::prepare_benchmark(); | ||
let pool_id = Helper::<T>::initialize_active_state(n); |
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.
@lemunozm I noticed that the loans benchmarks did parametrize apply_transfer_debt
which created compiler issues as the pallet_loans::weights::WeightInfo
expect the existence of a parameter. AFAICT, this provided solution should be appropriate. WDYT?
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.
My fault! You did the perfect fix for this! 💯
Thanks, and sorry for missing this
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.
LGTM, thanks for all the work on this @wischli !! 🚀
type TrancheId = TrancheId; | ||
type TrancheTokenPrice = PoolSystem; | ||
type TreasuryAccount = TreasuryAccount; | ||
type WeightInfo = (); |
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 have fear when I see the ()
type as it seems as if it's using Zero
weights. Maybe as a way of confirming the reading the weights have actually a value, we could name the type as DefensiveWeights
, and use it here.
type TokenSwapOrderId = u64; | ||
type TokenSwaps = OrderBook; | ||
type TrancheId = TrancheId; | ||
type WeightInfo = (); |
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.
Should WeightInfo
be removed if there are no extrinsics associated with this pallet?
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.
LGTM!
pallet_pool_system::Pool::<Runtime>::mutate(ANEMOY_POOL_ID, |maybe_details| { | ||
if let Some(details) = maybe_details { | ||
details.currency = CURRENCY_ID_DOT_NATIVE; | ||
log::info!("anemoy_pool::Migration: currency set to USDC ✓"); | ||
} else { | ||
log::warn!("anemoy_pool::Migration: Pool details empty, skipping migration"); | ||
} |
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.
Comment: This would have bricked Catalyst due to unwrapping a None
variant. We need to be more attentive of never unwrapping outside of tests.
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.
Thanks for the catch, @wischli. This is my bad but also reveals the necessity for a more formal review process and review requirements. In this case, requiring a migration on Centrifuge to be tested against Centrifuge AND Catalyst before being approved, whereas we only tested against Centrifuge.
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.
LGTM!
|
||
parameter_types! { | ||
pub const MaxIncomingMessageSize: u32 = 1024; | ||
pub Sender: AccountId = GatewayAccountProvider::<Runtime, LocationToAccountId>::get_gateway_account(); | ||
} | ||
|
||
impl pallet_liquidity_pools_gateway::Config for Runtime { | ||
type AdminOrigin = EnsureRoot<AccountId>; | ||
type InboundQueue = crate::LiquidityPools; | ||
type AdminOrigin = EnsureRootOr<HalfOfCouncil>; |
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.
Why half of council in dev? No blocker, just curious.
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.
Copy paste error. I had this file removed at some point. Would it be fine to fix this in a post-release PR?
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.
Of course. Root is still enabled so no problem.
} | ||
|
||
impl pallet_liquidity_pools::Config for Runtime { | ||
// NOTE: No need to adapt that. The Router is an artifact and will be removed |
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.
Artifact?
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.
Artifact indeed, sorry about that. Can I remove this in a post-release PR? CI takes ages as each push builds new images.
Next release I need to apply another branching strategy, i.e. have an rc
branch which wants to merge into release-vx.y.z
which is based on main
after feature freeze. This way, we don't need to rebase the rc
branch on any non release related push to main. However, merging the release branch into main
still creates CI overhead but I suppose that's fine.
Description
LPs
The following changes affect all runtimes:
StumpInboundQueue
and setsLiquidityPools
asInboundQueue
implementerOutboundQueue
UpdateTrancheInvestmentLimit
messageliquidity_pools
moduleUSDC
The following changes only affect
centrifuge
runtime:Runtime upgrade
Misc
pallet-loans
benchmark forapply_transfer_debt
which did not factor in a paremeter as defined in the correspondingWeightInfo
Checklist: