Fix EventQueue ClientFromHandler to Inject ent client | Enrich River Job submission with Listener Info#2070
Merged
golanglemonade merged 2 commits intomainfrom Feb 25, 2026
Merged
Conversation
golanglemonade
approved these changes
Feb 25, 2026
|
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
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.



gala's
ContextManager.Restorereconstructs auth claims and log fields from the durable snapshot, but the ent client is a live runtime dependency that isn't serializable - so it's absent from the restored context. Any downstream code callinggenerated.FromContext(ctx)(e.g., ent interceptors doing FGA/module checks) would get nil and fail. By seeding the client inClientFromHandler, all callers get an enriched context without needing per-handler boilerplate.Additionally, adds better logging into trust center listeners, enriches the River job submission with additional metadata.