passthrough scheme not documented

[rittneje]

As far as I can tell, the passthrough:/// scheme does not appear to be documented anywhere. It is needed in order to properly use the bufconn package.

It is mentioned in this comment: #7091 (comment)

It is not mentioned in the language agnostic gRPC docs. https://github.com/grpc/grpc/blob/master/doc/naming.md

[purnesh42H]

@rittneje yes, passthrough is only applicable in grpc-go and is already deprecated https://github.com/grpc/grpc-go/blob/master/resolver/passthrough/passthrough.go#L22. It only exist for backward compatibility right now.

[rittneje]

@purnesh42H First, the file you linked only mentions the package is deprecated and should not be imported. It doesn't mention anything about the scheme itself. Second, it is the only way to get bufconn to work, so you can't just deprecate it without a proper replacement. Please re-open this issue.

[dfinkel]

FWIW, my team switched our bufconn uses to localhost as the address, since that's guaranteed to resolve with the DNS resolver.

[purnesh42H]

yeah, its not explicitly documented that passthrough is deprecated apart from source code but that's because it is internal to grpc-go. In release 1.64, we deprecated grpc.Dial to use grpc.NewClient https://github.com/grpc/grpc-go/releases/tag/v1.64.0. With grpc.Dial the default resolution scheme is passthrough which uses passthrough resolver that i linked above. With grpc.NewClient the default scheme is dns. If you want to use passthrough with grpc.NewClient, you need to pass the adderss prefixed with passthrough:///.

Could you describe what issue you are facing with bufcon though?

[github-actions]

This issue is labeled as requiring an update from the reporter, and no update has been received after 6 days. If no update is provided in the next 7 days, this issue will be automatically closed.