Skip to content

fix: batcher update user_states atomically #1520

@uri-99

Description

@uri-99

When Batcher updates user_states, it does so in 3 steps.
Currently they are executed in series, and if one fails, the following ones will not execute
All 3 could be executed in the same self.user_states.entry(*addr) , ensuring atomicity in the transaction.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions