Skip to content
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.

Sign up for GitHub

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

Jump to bottom

blockchain, utreexobackends: move nodesmapslice and cachedleavesmapslice to utreexobackends #168

Merged
merged 2 commits into from
Apr 22, 2024
Merged

blockchain, utreexobackends: move nodesmapslice and cachedleavesmapslice to utreexobackends #168

merged 2 commits into from
Apr 22, 2024

Commits on Apr 22, 2024

  1. utreexobackends, blockchain: move nodesMapSlice to utreexobackends 

    Moving nodesMapSlice to a separate package ensures that private fields
don't get accessed and the code is safer for concurrency due to this.
This addresses a bug that was noticed that resulted in a runtime panic
due to concurrent access of a map in nodesMapSlice.
    @kcalvinalvin
    kcalvinalvin committed Apr 22, 2024
    Configuration menu
    Copy the full SHA
    917f1e1 View commit details
    Browse the repository at this point in the history

  2. blockchain, utreexobackends: move cached leaves map to utreexobackends 

    Moving cached leaves map to a separate package ensures that private
fields do not get accessed. This achieves better concurrency guarantees
as the exported functions of cached leaves map are concurrency safe but
if the fields get accessed directly, it bypasses the safety measures.
    @kcalvinalvin
    kcalvinalvin committed Apr 22, 2024
    Configuration menu
    Copy the full SHA
    8144ed9 View commit details
    Browse the repository at this point in the history