}
				}
			}
			s.RUnlock()

			resyncTimer.Reset(resyncTimeInterval)
		case <-ctx.Done():
			// server could be restarting - need
			// to exit immediately
			return
		}
	}
}

const (
	resyncWorkerCnt        = 10 // limit of number of bucket resyncs is progress at any given time

    assertFailsWith<IllegalStateException> {
      sinkReference.get().flush()
    }
    assertFailsWith<IllegalStateException> {
      sinkReference.get().write("ghi".toByteArray())
      sinkReference.get().emit()
    }
  }

  @Test
  fun getHeadersThrows() {
    server.enqueue(MockResponse.Builder().onRequestStart(CloseSocket()).build())
    assertFailsWith<IOException> {
      getResponse(newRequest("/"))

HSPLokio/AsyncTimeout$source$1;->close()V
HSPLokio/AsyncTimeout$source$1;->read(Lokio/Buffer;J)J
HSPLokio/AsyncTimeout;-><clinit>()V
HSPLokio/AsyncTimeout;-><init>()V
HSPLokio/AsyncTimeout;->enter()V
HSPLokio/AsyncTimeout;->exit()Z
HSPLokio/Buffer;-><init>()V
HSPLokio/Buffer;->exhausted()Z
HSPLokio/Buffer;->getByte(J)B
HSPLokio/Buffer;->indexOfElement(Lokio/ByteString;)J
HSPLokio/Buffer;->rangeEquals(JLokio/ByteString;)Z

containers can be added to running pods for purposes such as debugging, similar to how `kubectl exec` runs a process in an existing container. Also like `kubectl exec`, no resources are reserved for ephemeral containers and they are not restarted when they exit. Note that container namespace targeting is not yet implemented, so [process namespace sharing](https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/) must be enabled to view process from other containers in the pod. ([...

ˆOì}h?™ŽÜÐ¥é× ©R ’-ê É!U³ ©°X††¡.©ŒÐkŒ9†PÍB2 Ðn >²ú¬bæmHœ@¿oÏ « !ì X3=ÀÓºˆ. Ô‰ c3> ‹È~ ‹Pô ¯Ö¯tã >pZë˜{,5eä²x»2oUT®Ìô~ág™ Ú³sÜÉ×Þ³ñ6…q f‘Å &%øŒ ët™Ú)©ÄÌ wœ d”Ö(5êìázyBtí ’aYS±×jX_óÊM[&`®üÊÄécdÝ Ûà<”†¾— ±8”! ¿gVÙ· $0ƒÔ ©ÝW F[£C 7U#!z YñMƒå=y„ @*Ç ¢Ÿ× "êðÍÜ oÏÿâø/ ‰Á ¤Á{è ‘$aÃÕµO{1 ¨Û®5æ7J(hÔ ´JŽ„DŒÏ»_¦›&HÒþƒZ7Èk| § énaÁ™ È,µÕkø ŒV×# ̬U OÔW~ QãËàYwã ó °æ{P s%Ö|o=0{ dC ÉNcù©©u¾¬Ë6ÄÃ;'À Qñ R û¡°ö ­nž}? ˆMŽš an–¾8Y@€ õñ R ]ì‘Gi ã1ä‘þ†ŠÒ'ð;ƒ±ªìû„WMÐଞ7ùÅò'´B»£Ô4žùóR2”Bð ü ý ½·N¹Iƒ”)¹üÒì®’ òì ÉR5 -P}ŒI SjXÑê¡EDó<¿Œîh...

- Removed unused flags from `kubectl run` command. ([#110668](https://github.com/kubernetes/kubernetes/pull/110668), [@brianpursley](https://github.com/brianpursley))
- Run kubelet, when there is an error exit, print the error log. ([#110691](https://github.com/kubernetes/kubernetes/pull/110691), [@yangjunmyfm192085](https://github.com/yangjunmyfm192085))

- EndpointSlice controller is now less likely to emit FailedToUpdateEndpointSlices events. ([#100113](https://github.com/kubernetes/kubernetes/pull/100113), [@robscott](https://github.com/robscott)) [SIG Apps and Network]

- Kube-proxy no longer falls back from ipvs mode to iptables mode if you ask it to do ipvs but the system is not correctly configured. Instead, it will just exit with an error. ([#111806](https://github.com/kubernetes/kubernetes/pull/111806), [@danwinship](https://github.com/danwinship)) [SIG Network]

* Windows nodes on GCE use a known-working 1809 image rather than the latest 1809 image. ([#76722](https://github.com/kubernetes/kubernetes/pull/76722), [@pjh](https://github.com/pjh))
* kube-proxy: os exit when CleanupAndExit is set to true ([#76732](https://github.com/kubernetes/kubernetes/pull/76732), [@JieJhih](https://github.com/JieJhih))

- HPA controller will no longer emit a 'FailedRescale' event if a scale operation initially fails due to a conflict but succeeds after a retry; a 'SuccessfulRescale' event will be emitted instead. A 'FailedRescale' event is still emitted if retries are exhausted. ([#132007](https://g...