-
Notifications
You must be signed in to change notification settings - Fork 28
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
Return richer information on SyncSummary
#512
Comments
We may also consider the following structure: pub struct SyncSummary {
pub block_num: u32,
pub received_notes: Vec<NoteId>,
pub committed_notes: Vec<NoteId>,
pub consumed_notes: Vec<NoteId>,
pub updated_accounts: Vec<AccountId>,
pub committed_transactions: Vec<TransactionId>,
} |
Just to be clear, the change from |
I think this may be OK. With the refactoring we are discussing in #487 I think we'll be retrieving all relevant notes from the store anyways, then applying state transitions to them, and then saving them back to the store. So, the amount of work probably wouldn't be that different. |
Closed by #513 |
What should be done?
Currently, we are just returning basic flat stats on
SyncSummary
such as number of new notes, number of committed transactions, etc. We could improve this and return IDs of each of the involved entities.How should it be done?
Gather IDs of new entities and return them in
Vec<_>
fields. The struct should look something like:When is this task done?
When we return richer information on
SyncSummary
as described above. The CLI can keep its current functionality by showing the count of each of these fields.Additional context
No response
The text was updated successfully, but these errors were encountered: