This repository was archived by the owner on Feb 22, 2018. It is now read-only.
Serializing execution of transformers #889
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When executing under pub serve the order of apply for the transformers may not be the same as the phase ordering. This was causing deadlocks for the transformers sharing a resolver as the read of an asset for one transformer was invoking the apply for a different transformer, which would then deadlock waiting for the resolver.
blois
pushed a commit
that referenced
this pull request
Apr 11, 2014
When executing under pub serve the order of apply for the transformers may not be the same as the phase ordering. This was causing deadlocks for the transformers sharing a resolver as the read of an asset for one transformer was invoking the apply for a different transformer, which would then deadlock waiting for the resolver. Closes #889
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When executing under pub serve the order of apply for the transformers may not be the same as the phase ordering. This was causing deadlocks for the transformers sharing a resolver as the read of an asset for one transformer was invoking the apply for a different transformer, which would then deadlock waiting for the resolver.