Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Remove runtime registered extensions after execution #7236

Merged
4 commits merged into from
Oct 1, 2020

Conversation

bkchr
Copy link
Member

@bkchr bkchr commented Sep 29, 2020

This prevents a bug when an extension was registered in native, but the
native execution aborted without removing the extension again. Now, when
executing the wasm code the extension is still registered and it fails
of being registered. So, the wasm execution fails as well. This can
happen for example for the VerificationExt.

polkadot companion: paritytech/polkadot#1773

This prevents a bug when an extension was registered in native, but the
native execution aborted without removing the extension again. Now, when
executing the wasm code the extension is still registered and it fails
of being registered. So, the wasm execution fails as well. This can
happen for example for the `VerificationExt`.
@bkchr bkchr added A0-please_review Pull request needs code review. B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders. labels Sep 29, 2020
@bkchr bkchr requested a review from NikVolf September 29, 2020 21:41
@bkchr bkchr closed this Sep 30, 2020
bkchr added a commit to paritytech/polkadot that referenced this pull request Oct 1, 2020
@bkchr
Copy link
Member Author

bkchr commented Oct 1, 2020

bot merge

@ghost
Copy link

ghost commented Oct 1, 2020

Trying merge.

@ghost ghost merged commit 025dd54 into master Oct 1, 2020
@ghost ghost deleted the bkchr-clear-extensions branch October 1, 2020 09:12
ghost pushed a commit to paritytech/polkadot that referenced this pull request Oct 1, 2020
* Companion for paritytech/substrate#7236

* "Update Substrate"

Co-authored-by: parity-processbot <>
liuchengxu pushed a commit to liuchengxu/substrate that referenced this pull request Oct 5, 2020
* Remove runtime registered extensions after execution

This prevents a bug when an extension was registered in native, but the
native execution aborted without removing the extension again. Now, when
executing the wasm code the extension is still registered and it fails
of being registered. So, the wasm execution fails as well. This can
happen for example for the `VerificationExt`.

* Make it better
ordian added a commit to paritytech/polkadot that referenced this pull request Oct 6, 2020
* master:
  Make collation an optional return (#1787)
  XCM: Land xcm-handler and xcm-executor (#1771)
  v0.8.25 (#1785)
  add two node local net script (#1781)
  Adjust max nominators down to 128 (from 256) (#1782)
  Companion for substrate/pull/7215 (#1768)
  Remove Stale Upgrades (#1780)
  Update Polkadot Weights for Substrate 2.0 (#1761)
  Parachains v1 registrar module. (#1559)
  Derive `From` for `AllMessages` and simplify `send_msg` (#1774)
  implement remaining subsystem metrics (#1770)
  Companion for paritytech/substrate#7236 (#1773)
  WIP: remove deprecated only/except clauses, build is now manual on PRs (#1769)
  Increase Westend `spec_version` (#1766)
  move Metrics to utils (#1765)
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A0-please_review Pull request needs code review. B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants