You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BufferedBlockstore currently acts to cache all changes and write once the transition is confirmed valid (although can be used in many cases to avoid unnecessary writes)
// TODO update this to only write over values connected to the root
and explained at a high level what needs to be done.
Implementation is not set in stone, and I did chose to create the interface as flushing the store, but implementation could match go impls more closely by copying values from one blockstore (usally an in memory store) to another. I chose to go with this route to not need mutexes for the memory store (This is only used in sync context) and because it made more logical sense to be a flush.
This issue is borderline good first issue, but because of the complexity of parsing the IPLD for links and recursively retrieving, I won't mark as such
Other information and links
The text was updated successfully, but these errors were encountered:
Issue summary
BufferedBlockstore currently acts to cache all changes and write once the transition is confirmed valid (although can be used in many cases to avoid unnecessary writes)
I created the TODO in changes from #374 here:
forest/ipld/blockstore/src/buffered.rs
Line 31 in 1cef78c
Implementation is not set in stone, and I did chose to create the interface as flushing the store, but implementation could match go impls more closely by copying values from one blockstore (usally an in memory store) to another. I chose to go with this route to not need mutexes for the memory store (This is only used in sync context) and because it made more logical sense to be a flush.
This issue is borderline good first issue, but because of the complexity of parsing the IPLD for links and recursively retrieving, I won't mark as such
Other information and links
The text was updated successfully, but these errors were encountered: