Hubris-side changes for removing dispatch_n
in idol-runtime
#1632
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.
This is the Hubris part of oxidecomputer/idolatry#39, the description of which I've pasted below for your reference:
We ran into an issue last week where we inadvertently replaced a call to
idol_runtime::dispatch_n
with a call toidol_runtime::dispatch
. This difficult-to-spot two-character change has the following implications:This is bad, and caused real failures in host startup.
This change alters the API to eliminate
dispatch_n
and make notification handling mandatory for all Idol servers -- to opt out of receiving notifications, they must explicitly implementNotificationHandler
as stubs. This should prevent this class of error from reoccurring, and has the added benefit of simplifying the runtime implementation -- which I'd previously complicated in a misguided attempt at ergonomics.