Dhia Ayachi 5f6bf369af reset coalesceTimer to nil as soon as the event is consumed (#11924) ... * reset `coalesceTimer` to nil as soon as the event is consumed * add change log * refactor to add relevant test. * fix linter * Apply suggestions from code review Co-authored-by: Freddy <freddygv@users.noreply.github.com> * remove non needed check Co-authored-by: Freddy <freddygv@users.noreply.github.com>		2022-01-05 12:17:47 -05:00
..
connect_proxy.go	Clean up chains separately from their watches	2021-12-13 18:56:14 -07:00
ingress_gateway.go	Check ingress upstreams when gating chain watches	2021-12-13 18:56:28 -07:00
manager.go	reset coalesceTimer to nil as soon as the event is consumed (#11924)	2022-01-05 12:17:47 -05:00
manager_test.go	reset coalesceTimer to nil as soon as the event is consumed (#11924)	2022-01-05 12:17:47 -05:00
mesh_gateway.go
mesh_gateway_oss.go	re-run gofmt on 1.17 (#11579)	2021-11-16 12:04:01 -06:00
proxycfg.go
snapshot.go	Check ingress upstreams when gating chain watches	2021-12-13 18:56:28 -07:00
state.go	reset coalesceTimer to nil as soon as the event is consumed (#11924)	2022-01-05 12:17:47 -05:00
state_test.go	Account for new upstreams constraint in tests	2021-12-13 18:56:28 -07:00
terminating_gateway.go
testing.go	xds: prefer fed state gateway definitions if they're fresher (#11522)	2021-11-09 16:45:36 +00:00
upstreams.go	Purge chain if it shouldn't be there	2021-12-13 18:56:44 -07:00