Mike Spreitzer 3419387b18 Call queueSet::boundNextDispatchLocked enough ... Fix the one path where boundNextDispatchLocked was not being called after modifying a queue. Also check for negative work in a request. These are motivated by https://github.com/kubernetes/kubernetes/issues/112169 but I do not have a way to reproduce it and so can not check that these changes actually remove that symptom. But these changes are good anyway. Kubernetes-commit: 6ee93e2cee695203a6ce4935da1b9a807b624260		2022-09-01 22:54:53 -04:00
..
apihelpers	apf: update e2e test to use v1beta2	2021-08-16 17:12:42 -04:00
dryrun	Revert "remove unwanted values returned from dry-run"	2022-04-06 12:34:42 -04:00
feature	update import of generic featuregate code from k8s.io/apiserver/pkg/util/feature -> k8s.io/component-base/featuregate	2019-03-04 12:46:52 -05:00
flowcontrol	Call queueSet::boundNextDispatchLocked enough	2022-09-01 22:54:53 -04:00
flushwriter	sync: initially remove files BUILD */BUILD BUILD.bazel */BUILD.bazel	2018-03-15 09:38:17 +00:00
notfoundhandler	aggregator: pass apiServiceRegistrationControllerInitiated signal directly to apiserviceRegistration controller	2021-10-20 11:06:27 +02:00
openapi	add test case for enabled OpenAPIEnums	2022-03-22 17:58:16 -07:00
proxy	Improve the error message when trying to proxy unsupported service type	2021-11-17 12:24:49 +01:00
shufflesharding	Less demanding test cases in TestUniformDistribution	2021-01-25 01:44:08 -05:00
webhook	Generate and format files	2022-07-19 20:54:13 -04:00
wsstream	Generate and format files	2022-07-19 20:54:13 -04:00
x509metrics	Generate and format files	2022-07-19 20:54:13 -04:00