Fix concurrency issue when registering assets in AssetPipeline #141
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #66
Because HTTP server can accept multiple requests at the same time we can end up iterating assets concurrently and causing
System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
and it's probably also possible to create invalid state (duplicates).Switching to
ConcurrentDictionary
which protects from concurrent writes and also adds indexer to get route directly.