### Types of properties that should not use lazy types

The guidelines below do not apply to all properties. There are cases where the lazy types should not be used:

#### Non-calculated values

These are inappropriate uses of lazy types:

```groovy
class Example {
    Property<String> getSomeProperty()

    Example() {
        getSomeProperty().set("value")
        getSomeProperty().disallowChanges()
    }
}

        assertNotSame(target1, target2, "Instances should be different objects");
    }

    @Test
    public void test_class_has_proper_annotations() {
        // Verify the class doesn't have any inappropriate annotations
        assertFalse("Class should not be deprecated", HotThreadMonitorTarget.class.isAnnotationPresent(Deprecated.class));
    }

        assertNotSame(target1, target2, "Instances should be different objects");
    }

    @Test
    public void test_class_has_proper_annotations() {
        // Verify the class doesn't have any inappropriate annotations
        assertFalse("Class should not be deprecated", SystemMonitorTarget.class.isAnnotationPresent(Deprecated.class));
    }

    @Test

   * Returns an {@link Executor} that runs each task in the thread that invokes {@link
   * Executor#execute execute}, as in {@link CallerRunsPolicy}.
   *
   * <p>This executor is appropriate for tasks that are lightweight and not deeply chained.
   * Inappropriate {@code directExecutor} usage can cause problems, and these problems can be
   * difficult to reproduce because they depend on timing. For example:
   *
   * <ul>

    }
  }

  /*
   * Arguably we don't need a timed getUnchecked because any operation slow enough to require a
   * timeout is heavyweight enough to throw a checked exception and therefore be inappropriate to
   * use with getUnchecked. Further, it's not clear that converting the checked TimeoutException to
   * a RuntimeException -- especially to an UncheckedExecutionException, since it wasn't thrown by

- Fixed a bug that caused apiservers to send an inappropriate Content-Type request header to authorization, token authentication, imagepolicy admission, and audit webhooks when the alpha client-go feature gate "ClientsPreferCBOR" is enabled. ([#132960](https://github.com/kubernetes/kubernetes/pull/132960),...

In this case the middleware will intercept the incoming request and respond with appropriate CORS headers, and either a `200` or `400` response for informational purposes.

### Simple requests { #simple-requests }

Any request with an `Origin` header. In this case the middleware will pass the request through as normal, but will include appropriate CORS headers on the response.

## More info { #more-info }

Translate to Russian (русский язык).

Language code: ru.

---

Use a neutral tone (not overly formal or informal).

Use correct Russian grammar — appropriate cases, suffixes, and endings depending on context.

For the following technical terms, use these specific translations to ensure consistency and clarity across the documentation:

      }
      return this;
    }

    /**
     * Returns a newly-created {@code ImmutableCollection} of the appropriate type, containing the
     * elements provided to this builder.
     *
     * <p>Note that each builder class covariantly returns the appropriate type of {@code
     * ImmutableCollection} from this method.
     */
    public abstract ImmutableCollection<E> build();
  }

Language code: ko.

### Grammar and tone

- Use polite, instructional Korean (e.g. 합니다/하세요 style).
- Keep the tone consistent with the existing Korean FastAPI docs.
- Do not translate “You” literally as “당신”. Use “여러분” where appropriate, or omit the subject if it sounds more natural in Korean.

### Headings

- Follow existing Korean heading style (short, action-oriented headings like “확인하기”).
- Do not add trailing punctuation to headings.