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

Events to track extrinsic success #640

Merged
merged 4 commits into from
Aug 31, 2018
Merged

Events to track extrinsic success #640

merged 4 commits into from
Aug 31, 2018

Conversation

gavofyork
Copy link
Member

Currently it's rather difficult to know whether an extrinsic succeeded correctly of failed as a no-op for some reason. This remedies that using the existing events system.

It doesn't currently report the nature of the failure. That's a &'static str and not really suitable for reporting back to the chain. Some later refactor might change the standard error type into something resembling Event such that it can properly impl Encode/Decode, but for now we'll keep it simple.

@gavofyork gavofyork requested a review from arkpar August 31, 2018 14:57
@gavofyork gavofyork assigned gavofyork and unassigned gavofyork Aug 31, 2018
@gavofyork gavofyork requested a review from pepyakin August 31, 2018 14:57
@gavofyork gavofyork added the A0-please_review Pull request needs code review. label Aug 31, 2018
@pepyakin pepyakin added A8-looksgood and removed A0-please_review Pull request needs code review. labels Aug 31, 2018
@gavofyork gavofyork merged commit 6f5ac42 into master Aug 31, 2018
@gavofyork gavofyork deleted the gav-tx-success-event branch August 31, 2018 16:44
@emielsebastiaan
Copy link

Thank you for addressing this 😊

gguoss pushed a commit to chainx-org/substrate that referenced this pull request Sep 3, 2018
* Initial draft

* Fixes

* Extrinsic success events
dvdplm added a commit that referenced this pull request Sep 3, 2018
…rs-generic-over-hasher-and-rlpcodec

* origin/master: (26 commits)
  Contract runtime polishing (#601)
  WIP on chain heap (#639)
  Events to track extrinsic success (#640)
  Install llvm-tools-preview component (#643)
  fix wasm executor compile error (#631)
  random fixes (#638)
  Empty becomes (), reflecting convention (#637)
  Allow to build_upon skipped entries, but don't walk back (#635)
  Separate out staking module into balances and payment (#629)
  Update .gitlab-ci.yml (#633)
  Do not attempt to rustup if in CI. This is taken care of by the base (#621)
  Avoid need for ident strings in storage (#624)
  rename to panic_handler as panic_implementation is deprecated in nightly (#626)
  5 random fixes (#2) (#623)
  fix one typo in README (#627)
  Misspelled words (#625)
  Contracts: Per block gas limit (#506)
  Make sure to ban invalid transactions. (#615) (#620)
  Forward-port BFT fixes from v0.2 and restructure agreement cancelling (#619)
  Allow specifying listening multiaddresses (#577)
  ...
dvdplm added a commit that referenced this pull request Sep 4, 2018
* master: (22 commits)
  Introduce treasury and document (#646)
  Off-the-table staking preference (#656)
  Implement function `json_metadata` in `decl_module!` (#654)
  Fix warnings in networking (#652)
  Add a reputation system (#645)
  Check for pruned block state (#648)
  Contract runtime polishing (#601)
  WIP on chain heap (#639)
  Events to track extrinsic success (#640)
  Install llvm-tools-preview component (#643)
  fix wasm executor compile error (#631)
  random fixes (#638)
  Empty becomes (), reflecting convention (#637)
  Allow to build_upon skipped entries, but don't walk back (#635)
  Separate out staking module into balances and payment (#629)
  Update .gitlab-ci.yml (#633)
  Do not attempt to rustup if in CI. This is taken care of by the base (#621)
  Avoid need for ident strings in storage (#624)
  rename to panic_handler as panic_implementation is deprecated in nightly (#626)
  5 random fixes (#2) (#623)
  ...
liuchengxu added a commit to chainx-org/substrate that referenced this pull request Aug 23, 2021
* Fix money field missing

* Rename address to account in RPC

* Rename TeamAddress and CouncilAddress to TeamAccount and CouncilAccount

* Build wasm
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants