lose watch when SimpleCache respond return false in respondWithSpecificOrder #219

Activity

1. staticfinalzero

   added 2 commits that reference this issue on May 17, 2024

   bug fix to requested resource does not exist handling

   ...

   7be0ae8

   cache: bug fix to requested resource does not exist handling

   ...

   26eba64
2. staticfinalzero commented on May 17, 2024

   

   staticfinalzero

   on May 17, 2024

   Last edited by staticfinalzero

   More actions

   We've also encountered this issue when using gRPC with xDS. If we try to send a gRPC request through to xds:///abc before the SimpleCache has that resource available, subsequent calls to SimpleCache.setSnapshot() will remove the watch preventing gRPC from being notified of later updates to the abc resource.

   Per the Envoy specs at https://www.envoyproxy.io/docs/envoy/latest/api-docs/xds_protocol#knowing-when-a-requested-resource-does-not-exist, this should be considered a bug:

   Note that even if a requested resource does not exist at the moment when the client requests it, that resource could be created at any time. Management servers must remember the set of resources being requested by the client, and if one of those resources springs into existence later, the server must send an update to the client informing it of the new resource.

   I've submitted a pull request here: #373
3. staticfinalzero

   added a commit that references this issue on Jun 26, 2024

   cache: bug fix to requested resource does not exist handling

   ...

   272d28f