previous-next-scan.svg...

    Previously, each domain name had its own virtual host. As an optimization, multiple domains may use a single virtual host.
    This means that a Envoy Filter previously matching a specific virtual host may now apply to more domains than in previous releases.

// Issue 1871.

package p

type a interface {
	foo(x int) (x int) // ERROR "duplicate argument|redefinition|redeclared"
}

/*
Previously:

bug.go:1 x redclared in this block
    previous declaration at bug.go:1

   *
   * <p>{@code putInstance(Foo.class, foo)} is equivalent to {@code
   * putInstance(TypeToken.of(Foo.class), foo)}.
   *
   * @return the value previously associated with this class (possibly {@code null}), or {@code
   *     null} if there was no previous entry.
   */
  @CanIgnoreReturnValue
  @CheckForNull
  <T extends B> T putInstance(Class<@NonNull T> type, @ParametricNullness T value);

  /**

   *
   * <p>{@code putInstance(Foo.class, foo)} is equivalent to {@code
   * putInstance(TypeToken.of(Foo.class), foo)}.
   *
   * @return the value previously associated with this class (possibly {@code null}), or {@code
   *     null} if there was no previous entry.
   */
  @CanIgnoreReturnValue
  @CheckForNull
  <T extends B> T putInstance(Class<@NonNull T> type, @ParametricNullness T value);

  /**

// Return a new status object.
TF_CAPI_EXPORT extern TF_Status* TF_NewStatus(void);

// Delete a previously created status object.
TF_CAPI_EXPORT extern void TF_DeleteStatus(TF_Status*);

// Record <code, msg> in *s.  Any previous information is lost.
// A common use is to clear a status: TF_SetStatus(s, TF_OK, "");
TF_CAPI_EXPORT extern void TF_SetStatus(TF_Status* s, TF_Code code,

    content: |
      In previous versions of Istio, tracing was automatically configured to send traces to `zipkin.istio-system.svc`.
      This default setting has been removed; users will need to explicitly configure where to send traces moving forward.

      `istioctl x precheck --from-version=1.21` can automatically detect if you may be impacted by this change.

// later, without having to re-write the data previously written to the hash.
// The hash state may contain portions of the input in its original form,
// which users are expected to handle for any possible security implications.
//
// Compatibility: Any future changes to hash or crypto packages will endeavor
// to maintain compatibility with state encoded using previous versions.

upgradeNotes:
  - title: "`base` Helm Chart removals"
    content: |
      A number of configurations previously present in the the `base` Helm chart were *copied* to the `istiod` chart in a previous releases.

      In this release, the duplicated configurations are fully removed from the `base` chart.

      Below shows a mapping of old configuration to new configuration:

     */
    enum ExecutionOutcome {
        /**
         * The outputs haven't been changed, because the work is already up-to-date
         * (i.e. its inputs and outputs match that of the previous execution in the
         * same workspace).
         */
        UP_TO_DATE,

        /**
         * The outputs of the work have been loaded from the build cache.
         */
        FROM_CACHE,