-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Align Events between Bulletin and SDK #10445
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
Conversation
|
/cmd prdoc --audience runtime_dev --bump patch |
|
All GitHub workflows were cancelled due to failure one of the required jobs. |
| log = { workspace = true } | ||
| pallet-balances = { workspace = true } | ||
| scale-info = { features = ["derive"], workspace = true } | ||
| serde = { optional = true, workspace = true, default-features = true } | ||
| sp-inherents = { workspace = true } | ||
| sp-io = { workspace = true } | ||
| sp-runtime = { workspace = true } | ||
| sp-transaction-storage-proof = { workspace = true } | ||
| tracing = { workspace = true } |
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 do you remove log and add tracing here? I don't see tracing added anywhere else except for this file
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.
Make it consistent with the Bulletin chain repo. If you prefer, I can remove tracing, and then add it back later when it's needed.
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.
Cool, I don't mind having this change as part of this PR but, please, make sure to mention this change in the PR description or the prdoc file (or both 🙃)
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.
because when I see something like this - first thing that comes to mind - is that it was an unintentional change
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.
Updated the PR desc and PRDoc: be7c1c6
|
/cmd bench --pallet pallet_transaction_storage |
|
Command "bench --pallet pallet_transaction_storage" has started 🚀 See logs here |
|
Command "bench --pallet pallet_transaction_storage" has failed ❌! See logs here |
@raymondkfcheung this won't work, you need to use |
hash field to Event::Stored and Event::Renewed* Align events between Bulletin and SDK * Extends `Stored` and `Renewed` events with a `hash: ContentHash` field. * Replaces `log` with `tracing` to match Bulletin’s logging approach. Addresses paritytech/polkadot-bulletin-chain#86, paritytech/polkadot-bulletin-chain#123 Relates to - [x] paritytech/polkadot-bulletin-chain#124 - [x] paritytech/polkadot-bulletin-chain#127 - [x] paritytech/polkadot-bulletin-chain#129 --------- Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com> (cherry picked from commit f757162)
|
Successfully created backport PR for |
StoredandRenewedevents with ahash: ContentHashfield.logwithtracingto match Bulletin’s logging approach.Addresses paritytech/polkadot-bulletin-chain#86, paritytech/polkadot-bulletin-chain#123
Relates to
hashfield toEvent::StoredandEvent::Renewedpolkadot-bulletin-chain#124content_hashpolkadot-bulletin-chain#129