cerc-io/go-ethereum
18
0
Fork 0
Code Issues 9 Pull Requests Packages Projects Releases 66 Wiki Activity

Emit storage diffs during full sync to rpc subscription #13

New Issue
Closed
opened 2019-09-13 17:48:57 +00:00 by rmulhol · 2 comments
rmulhol commented 2019-09-13 17:48:57 +00:00 (Migrated from github.com)
Copy Link

Hi there,

please note that this is an issue tracker reserved for bug reports and feature requests.

For general questions please use the gitter channel or the Ethereum stack exchange at https://ethereum.stackexchange.com.

System information

Geth version: geth version
OS & Version: Windows/Linux/OSX
Commit hash : (if develop)

Expected behaviour

Actual behaviour

Steps to reproduce the behaviour

Backtrace

[backtrace]
Hi there, please note that this is an issue tracker reserved for bug reports and feature requests. For general questions please use the gitter channel or the Ethereum stack exchange at https://ethereum.stackexchange.com. #### System information Geth version: `geth version` OS & Version: Windows/Linux/OSX Commit hash : (if `develop`) #### Expected behaviour #### Actual behaviour #### Steps to reproduce the behaviour #### Backtrace ```` [backtrace] ````
i-norden commented 2019-09-30 18:24:21 +00:00
Member
Copy Link

Are these not covered by the statediffing service? Or are these issues for separate, minimal, individual rpc methods for state and storage diffs?

Are these not covered by the statediffing service? Or are these issues for separate, minimal, individual rpc methods for state and storage diffs?
rmulhol commented 2019-10-01 01:04:55 +00:00 (Migrated from github.com)
Copy Link

Yep, the latter. Doesn't necessarily need to be a separate rpc method if it could be an argument to #11 (which addresses #12), but the idea here is to emit this data with a minimal code diff - ideally grabbing data that's already accessed during a sync.

Yep, the latter. Doesn't necessarily need to be a separate rpc method if it could be an argument to #11 (which addresses #12), but the idea here is to emit this data with a minimal code diff - ideally grabbing data that's already accessed during a sync.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

   
critical

   
duplicate

   
enhancement

   
epic

   
help wanted

   
in progress

   
invalid

   
low priority

   
question

   
rebase

   
v1

   
v5

   
wontfix
  
Copied from Github

An issue or PR manually copied from GitHub.

  
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
bug
critical
duplicate
enhancement
epic
help wanted
in progress
invalid
low priority
question
rebase
v1
v5
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/go-ethereum#13
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?