Repository navigation
Conversation
Contributor
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.
A service can declare its own REST or Connect listener while disabling generated scaffolding. Runtime.Init previously excluded those conventional names unconditionally, so the service received no listener binding although the endpoint was declared and advertised.
Exclude only endpoint identities already exported by the conventional setup. A declared service-owned listener now receives the same resolved binding as other named listeners. No service-specific port or configuration is added.
Classification: fix in the service agent that owns listener injection.
Validation: the regression fails before the change and passes after it; focused Init/named-endpoint tests pass with race detection for native and container contexts. Build and vet pass. Container-context initialization is not a running-container test. Full Docker lifecycle and packaging-image suites were not run for this change.