Brings back EventPersister
in discovery of background services
#17240
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.
In the prior work on this (#16913) we needed to
maintain an explicit set of modules from which to discover services, and
I missed the modules that include the
EventPersister
and theEventLogger
(a debugging-only service). This meant that under mostcircumstances, because the
event_persister
module wasn't imported, wewouldn't run it in either API or background processes.
Here I'm adding a test that confirms the exact subsets of services we
should run, just to avoid any quiet failures like this.
Checklist
<link to issue>
"mint.json
.