You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the gRPC-request cache limits functionality for stub testing.
Example scenario: gRPC server has several different services and each one has a own proto file.
The current cache implementation will cache a gRPC's services based on ip + port.
So if a stub is loaded and executed against gRPC server the cache gets populated, for next request the gRPC will check that this ip + port is in cache. However, the correct stub will not be in cache since only one proto file has been loaded.
The text was updated successfully, but these errors were encountered:
Currently the gRPC-request cache limits functionality for stub testing.
Example scenario: gRPC server has several different services and each one has a own proto file.
The current cache implementation will cache a gRPC's services based on ip + port.
So if a stub is loaded and executed against gRPC server the cache gets populated, for next request the gRPC will check that this ip + port is in cache. However, the correct stub will not be in cache since only one proto file has been loaded.
The text was updated successfully, but these errors were encountered: