matchers. class DiagnosingMatcher<T> TODO(ngd): Document. class FeatureMatcher<T,U> Supporting class for matching a feature of an object. class TypeSafeDiagnosingMa<T> Convenient base class for Matchers that require a non-null value of a specific type and that will report why the received value has been rejected. class TypeSafeMatcher<T> Convenient base class for Matchers that require a non-null value of a specific type. Uses of BaseMatcher in org.hamcrest.core Subclasses of BaseMatcher in org.hamcrest.core...

where the Image of the Sun formed by the refracted Light stood still between its two contrary Motions, in the common Period of its Progress and Regress; and when the Image fell upon that Place, I made fast the Prism. And in this Posture, as the most convenient, it is to be understood that all the Prisms are placed in the following Experiments, unless where some other Posture is described. The Prism therefore being placed in this Posture, I let the refracted Light fall perpendicularly upon a Sheet of white...

//
//	my/main/module
//	golang.org/x/text v0.3.0 [v0.4.0] => /tmp/text
//	rsc.io/pdf v0.1.1 (retracted) [v0.1.2]
//
// (For tools, 'go list -m -u -json all' may be more convenient to parse.)
//
// The -versions flag causes list to set the Module's Versions field
// to a list of all known versions of that module, ordered according

     * ensure that completed write operations performed by other threads are noticed. For most
     * purposes, the "count" field, tracking the number of elements, serves as that volatile
     * variable ensuring visibility. This is convenient because this field needs to be read in many
     * read operations anyway:
     *
     * - All (unsynchronized) read operations must first read the "count" field, and should not look
     * at table entries if it is 0.

     * ensure that completed write operations performed by other threads are noticed. For most
     * purposes, the "count" field, tracking the number of elements, serves as that volatile
     * variable ensuring visibility. This is convenient because this field needs to be read in many
     * read operations anyway:
     *
     * - All (unsynchronized) read operations must first read the "count" field, and should not look
     * at table entries if it is 0.

          }
        },
        "type": "object"
      },
      "io.k8s.apimachinery.pkg.api.resource.Quantity": {

			// It doesn't actually make sense to short-circuit here, since if
			// you connect directly to a NodePort from outside the cluster,
			// you only get the local endpoints. But it's simpler for us and
			// slightly more convenient for users to have this case get
			// short-circuited too.
			output: "10.180.0.2:80, 10.180.1.2:80",
			masq:   false,
		},
		{
			name:     "pod to LB with eTP:Local",
			sourceIP: "10.0.0.2",

          "current"
        ],
        "type": "object"
      },
      "io.k8s.apimachinery.pkg.api.resource.Quantity": {

        }
      },
      "type": "object"
    },
    "io.k8s.apimachinery.pkg.api.resource.Quantity": {

manifests/helm-profiles/README.md # Helm Profiles This folder provides a variety of "profiles" for helm installation. While a user can just explicitly pass this with `--values/-f`. However, Istio also provides a feature to bundle these with the charts, which is convenient when installing from remote charts. For details, see `copy-templates` Makefile target, and `manifests/zzz_profile.yaml`. Any changes to this folder should have a `make copy-templates` applied afterwards. Warning: unlike the `IstioOperator` profiles,...