```console
$ pip install websockets

---> 100%
```

</div>

## WebSockets client { #websockets-client }

### In production { #in-production }

In your production system, you probably have a frontend created with a modern framework like React, Vue.js or Angular.

And to communicate using WebSockets with your backend you would probably use your frontend's utilities.

    initialization order of companion objects.


## Version 4.7.1

_2020-05-18_

 *  Fix: Pass the right arguments in the trust manager created for `addInsecureHost()`. Without the
    fix insecure hosts crash with an `IllegalArgumentException` on Android.


## Version 4.7.0

_2020-05-17_

Persistent Volume Claims ## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/ ## persistence: enabled: true annotations: {} ## A manually managed Persistent Volume and Claim ## Requires persistence.enabled: true ## If defined, PVC must be created manually before volume will be bound existingClaim: "" ## minio data Persistent Volume Storage Class ## If defined, storageClassName: <storageClass> ## If set to "-", storageClassName: "", which disables dynamic provisioning ## If undefined (the default)...

Persistent Volume Claims ## ref: http://kubernetes.io/docs/user-guide/persistent-volumes/ ## persistence: enabled: true annotations: {} ## A manually managed Persistent Volume and Claim ## Requires persistence.enabled: true ## If defined, PVC must be created manually before volume will be bound existingClaim: "" ## minio data Persistent Volume Storage Class ## If defined, storageClassName: <storageClass> ## If set to "-", storageClassName: "", which disables dynamic provisioning ## If undefined (the default)...

    public void test_constructor_isQueryTrueNoExistingFieldLogs() {
        queryContext = new QueryContext("test", true);
        assertEquals("test", queryContext.getQueryString());

        // Verify that field logs are created
        Object fieldLogs = getMockRequest().getAttribute(Constants.FIELD_LOGS);
        assertNotNull(fieldLogs);
        assertTrue(fieldLogs instanceof Map);
    }

    // Test setQueryBuilder and getQueryBuilder

            addLenient(line.substring(0, index), line.substring(index + 1))
          }
          line[0] == ':' -> {
            // Work around empty header names and header names that start with a colon (created by old
            // broken SPDY versions of the response cache).
            addLenient("", line.substring(1)) // Empty header name.
          }
          else -> {
            // No header name.

        // SmbInfoAllocation.decode() always returns 20 bytes regardless of len parameter
        assertEquals(20, bytesRead);
        assertNotNull(response.getInfo());

        // The info should be created with zero values
        SmbInfoAllocation info = (SmbInfoAllocation) response.getInfo();
        assertEquals(0, info.getCapacity());
        assertEquals(0, info.getFree());
    }

    @Test

		storageLogIf(GlobalContext, fmt.Errorf("unable to create (%s) %w, drive may be faulty, please investigate",
			pathJoin(diskPath, minioMetaTmpBucket),
			err))
	}

	// Delete all temporary files created for DirectIO write check
	files, _ := filepath.Glob(filepath.Join(diskPath, ".writable-check-*.tmp"))
	for _, file := range files {
		go removeAll(file)
	}

your code interacts with the filesystem, network, etc. and uses checkpointed
variables as part of those interactions (ex: using a string variable to build a
filesystem path), a maliciously created checkpoint might be able to change the
targets of those operations, which could result in arbitrary
read/write/executions.

### Running a TensorFlow server

     *
     * @return error count
     */
    public long getOperationErrors() {
        return operationErrors.get();
    }

    /**
     * Get total number of connections created
     *
     * @return connection count
     */
    public long getConnectionsCreated() {
        return connectionsCreated.get();
    }

    /**
     * Get number of currently active connections