Skip to content

Preserve newer chain and node events during refresh #38

Description

@HDauven

A delayed refresh() can overwrite newer chain/node events from the same provider. The stale node URL also affects subsequent DuskApp reads.

Fix: guard network-state publication against intervening network changes, not only provider switches.

Check: delay refresh, change chain and node, then release the old response; SDK state and subsequent reads must retain the newer network.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions