Skip to content

ConfigurationProviders may miss mutliple notifications #617

Description

@ajcvickers

For example, see CreatingOptionalFileInNonExistentDirectoryWillReload. In this test there is a missing directory which is then created and a file is created in it. When this is run without any delays it can miss the notification of the file creation entirely. That is, no matter how long we wait, it will never happen. I haven't fully root-caused this, but it appears to be partly an issue with how change tokens are processed and then re-created asynchronously. It appears this can sometimes leave the application with the wrong change token, or can leave configuration not waiting on the current change token.

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