-
Notifications
You must be signed in to change notification settings - Fork 345
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
Dependency (Substrate/Polkadot/Frontier/Cumulus/...) update to v0.9.40 #2202
Conversation
It seems to fail with |
I also tried
|
build works now, but warp-sync still fails with:
|
@girazoki the test for XCM fails
The test is supposed to be computing the weight but I don't understand what it gets wrong |
This reverts commit 882b85e.
Coverage generated "Thu May 25 07:47:38 UTC 2023": Master coverage: 72.61% |
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. I'm concerned about some of the new proof_size benchmark values, do you think they might reduce block fullness if they are overestimates? (If they're underestimates, they're still better than 0
...) See my other comment for more context.
// Measured: `2479 + x * (79 ±0) + y * (38 ±0)` | ||
// Estimated: `32988 + x * (405 ±0) + y * (195 ±0)` | ||
// Minimum execution time: 94_976_000 picoseconds. | ||
Weight::from_parts(83_764_148, 32988) |
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 storage_proof size is probably excessively high because it depends on at least one Vec
in storage... eww.
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.
Notice that the generated code here has _
separators for time but not proof size. I'm guessing Parity doesn't have many benchmarks where proof_size > 999
...
@@ -290,6 +290,17 @@ export class XcmFragment { | |||
return this; | |||
} | |||
|
|||
// Add one or more `BuyExecution` instruction |
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.
// Add one or more `BuyExecution` instruction | |
// Add one or more `RefundSurplus` instruction(s) |
.joinCandidates(MIN_GLMR_STAKING, maxDelegationsPerDelegator) | ||
.signAsync(randomCandidate) | ||
// We split the candidates since they won't fit in a single block | ||
for (const randomCandidatesChunk of chunk(randomCandidates, 50)) { |
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 test always breaks, hopefully this alleviates that! 👍
T::Erc20TransferGasLimit::get().saturating_mul(T::WeightPerGas::get().ref_time()), | ||
0, |
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.
@librelois is 0 good 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.
Good catch, it's not good, I will fix that on a follow up PR
* update to v0.9.40 * update benchmarking weight template * fix build * make test compile * Includes page heap fixes * compile runtime-benchmarks * make warp sync work * toml sort * fix editorconfig * use new substrate version * fix warp sync * sort * fix --dev * remove duplicate SetMembersOrigin * toml-sort * remove kitchensink-runtime * fix builkd * use new weights * set manual weights for xcm fungible * use Weight::from_parts * use 0 pov_size for ref_time weight * update nimbus * exclude generated weight files from editorconfig * fmt * fmt * fix rust tests * fix import * fix tests * use Weight part pov_size to 0 * make dalek test work * fix transfer tests * use BoundedVec for auto compound delegations * fix modexp test * fix modexp test * fix tests * fix weight tests * fix staking tests via chunking * fix modexp test * fix lint and test * fix rust weight tests * fix partial ts tests * temp fix for xcm v2 * Fixes weight until benchmarking is fixed * set manual weight, fix ts tests * Adds temp hack for xcm tests * Use RefundSurplus as the no-op for saturating the queue, which does not have pov * Update evm to 0.39 * Revert "Update evm to 0.39" This reverts commit 882b85e. * upgrade polkadot for better support of xcm v2 * prettier * prettier * Revert temp fix for XCM weight * upgrade polkadot fork * Fixing hrmp-mock tests * clean up * prettier --------- Co-authored-by: crystalin <alan.sapede@gmail.com> Co-authored-by: librelois <c@elo.tf> Co-authored-by: girazoki <gorka.irazoki@gmail.com> Co-authored-by: tgmichel <telmo@purestake.com>
What does it do?
Important Changes
Substrate
pallet-random-collective-flip
to Insecure... paritytech/substrate#13301pallet-randomness-collective-flip
topallet-insecure-randomness-collective-flip
to state the fact that the pallet should not be used for production use-cases.sc-finality-grandpa
tosc-consensus-grandpa
FungiblesAdapter
s support +WeightTrader::buy_weight
more accurate error paritytech/polkadot#6739MatchError::AssetNotFound
>MatchError::AssetNotHandled
SetMembersOrigin
new typeSubmitOrigin
KeyIterators
Rework storage iterators paritytech/substrate#13284, Fix thestorage_size
/state_getStorageSize
RPC call paritytech/substrate#13154storage_keys
,storage_pairs
,child_storage_keys
.sc-network-common
back tosc-network
paritytech/substrate#13592sc-network-common
is moved tosc-network
sc-network
paritytech/substrate#12828sc-network
Cumulus
polkadot-service
paritytech/cumulus#2287RelayChainError::Application
toRelayChainError::ServiceError
(affectsnimbus
)Frontier