order async messages, provide workaround flag #1636
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
Having async messages run in parallel by default is confusing. It used to be the fact that there would be no way to delay a message response without async behaving out of order. We now have the ability, via explicit_response_port=True, to choose to defer when to respond to a message. This lets you just create_task to parallelize message handling. This adds a workaround flag just in case we need to keep someone internally on the old behavior. Differential Revision: [D85172238](https://our.internmc.facebook.com/intern/diff/D85172238/) **NOTE FOR REVIEWERS**: This PR has internal Meta-specific changes or comments, please review them on [Phabricator](https://our.internmc.facebook.com/intern/diff/D85172238/)! [ghstack-poisoned]
zdevito
added a commit
that referenced
this pull request
Oct 21, 2025
Having async messages run in parallel by default is confusing. It used to be the fact that there would be no way to delay a message response without async behaving out of order. We now have the ability, via explicit_response_port=True, to choose to defer when to respond to a message. This lets you just create_task to parallelize message handling. This adds a workaround flag just in case we need to keep someone internally on the old behavior. Differential Revision: [D85172238](https://our.internmc.facebook.com/intern/diff/D85172238/) **NOTE FOR REVIEWERS**: This PR has internal Meta-specific changes or comments, please review them on [Phabricator](https://our.internmc.facebook.com/intern/diff/D85172238/)! ghstack-source-id: 317770674 Pull Request resolved: #1636
meta-cla
bot
added
the
CLA Signed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Stack from ghstack (oldest at bottom):
Having async messages run in parallel by default is confusing. It used to be the fact that there would be no way to delay a message response without async behaving out of order. We now have the ability, via explicit_response_port=True, to choose to defer when to respond to a message. This lets you just create_task to parallelize message handling. This adds a workaround flag just in case we need to keep someone internally on the old behavior.
Differential Revision: D85172238
NOTE FOR REVIEWERS: This PR has internal Meta-specific changes or comments, please review them on Phabricator!