Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Make CallCredentials non-experimental

See original GitHub issue

This is a tracking issue for removing @ExperimentalApi from CallCredentials-related API.

Issue Analytics

State:
Created 7 years ago
Comments:11 (11 by maintainers)

Top GitHub Comments

1reaction

ejona86commented, Aug 4, 2022

API review:

Ready to stabilize
Obviously will remove the thisUsesUnstableApi() method. Probably in two phases: give it an implementation and make it deprecated, later delete.

0reactions

ejona86commented, Jan 16, 2018

Hmm… maybe that is an internal API. Because I also see this API which doesn’t have a cancel.

Top Results From Across the Web

CallCredentials (grpc-all 1.51.0 API)

Carries credential data that will be propagated to the server via request metadata for each RPC. This is used by CallOptions.withCallCredentials(io.grpc.

commit - Google Git

With this experiment gRPC uses CFStream API to make TCP + connections. ... either promote + to non-experimental or remove it.

grpc-java CallCredentials without thisUsesUnstableApi?

My question is: the only way I've seen so far to set Metadata headers for outgoing gRPC calls is to make a subclass...

io.grpc:grpc-services: Versions | Openbase

core: Fix CompositeChannelCredentials to no longer use CallCredentials for OOB channels. ... api, core: make channel logger accessible through NameResolver.

CVS log for pkgsrc/net/py-grpcio-tools/Makefile

The following binary pods are made available for ObjC V1 & V2 API gRPC-XCFramework ... C++ Promote ClientContext::set_wait_for_ready to be non-experimental.