* common ways to create a {@code ListenableFuture} include instantiating a {@link SettableFuture},
 * submitting a task to a {@link ListeningExecutorService}, and deriving a {@code Future} from an
 * existing one, typically using methods like {@link Futures#transform(ListenableFuture,
 * com.google.common.base.Function, java.util.concurrent.Executor) Futures.transform} and {@link

func (c *Connection) reconnected() {
	c.updateState(StateConnectionError)
	c.reconnects.Add(1)

	// Drain the outQueue, so any blocked messages can be sent.
	// We keep the queue, but start draining it, if it gets full.
	stopDraining := make(chan struct{})
	var wg sync.WaitGroup
	wg.Add(1)
	defer func() {
		close(stopDraining)
		wg.Wait()
	}()
	go func() {
		defer wg.Done()
		for {

// Debian : https://www.debian.org/
// Submitted by Peter Palfrader / Debian Sysadmin Team <******@****.***>
debian.net

// Definima : http://www.definima.com/
// Submitted by Maxence Bitterli <maxence@definima.com>
definima.io
definima.net

// Deno Land Inc : https://deno.com/
// Submitted by Luca Casonato <******@****.***>
deno.dev
deno-staging.dev

de
de.com
de.cool
de.eu.org
de.trendhosting.cloud
de.us
deal
dealer
deals
deatnu.no
debian.net
deca.jp
deci.jp
dedibox.fr
dedyn.io
def.br
definima.io
definima.net
degree
delhi.in
delivery
dell
dell-ogliastra.it
dellogliastra.it
deloitte
delta
demo.datacenter.fi
demo.datadetect.com
demo.jelastic.com
democracia.bo

de
de.com
de.cool
de.eu.org
de.trendhosting.cloud
de.us
deal
dealer
deals
deatnu.no
debian.net
deca.jp
deci.jp
dedibox.fr
dedyn.io
def.br
definima.io
definima.net
degree
delhi.in
delivery
dell
dell-ogliastra.it
dellogliastra.it
deloitte
delta
demo.datacenter.fi
demo.datadetect.com
demo.jelastic.com
democracia.bo

Continuous integration builds have used the following versions of external dependencies, however, this is not a strong recommendation and users should consult an appropriate installation or upgrade guide before deciding what versions of etcd, docker or rkt to use.

* Docker versions 1.10.3 - 1.12.3
  * Docker version 1.11.2 known issues

- Fix a regression where the Kubelet failed to exclude already completed pods from calculations about how many resources it was currently using when deciding whether to allow more pods. ([#104577](https://github.com/kubernetes/kubernetes/pull/104577), [@smarterclayton](https://github.com/smarterclayton))

- [Kube-proxy]: Implemented connection draining for terminating nodes. ([#116470](https://github.com/kubernetes/kubernetes/pull/116470), [@alexanderConstantinescu](https://github.com/alexanderConstantinescu))

Continuous integration builds have used the following versions of external dependencies, however, this is not a strong recommendation and users should consult an appropriate installation or upgrade guide before deciding what versions of etcd, docker or rkt to use.

* Docker versions 1.10.3, 1.11.2, 1.12.6 have been validated

    * Docker version 1.12.6 known issues

        * overlay2 driver not fully supported

Continuous integration builds use Docker versions 1.11.2, 1.12.6, 1.13.1,
and 17.03.2. These versions were validated on Kubernetes 1.8. However,
consult an appropriate installation or upgrade guide before deciding what
versions of Docker to use.

- Docker 1.13.1 and 17.03.2

    - Shared PID namespace, live-restore, and overlay2 were validated.

    - **Known issues**