public class samr {

    /**
     * Private constructor to prevent instantiation of utility class.
     */
    private samr() {
        // Utility class
    }

    /**
     * Returns the RPC interface syntax UUID and version for SAMR protocol.
     *
     * @return The SAMR interface UUID string
     */
    public static String getSyntax() {
        return "12345778-1234-abcd-ef00-0123456789ac:1.0";
    }

* The docs should include a source example file, not write Python directly in Markdown.
* If the source example(s) file can have different syntax for different Python versions, there should be different versions of the file, and they should be shown in tabs in the docs.
* There should be tests testing the source example.
* Before the PR is applied, the new tests should fail.

This also applies to `response_model_by_alias` that works similarly.

///

{* ../../docs_src/response_model/tutorial005_py310.py hl[29,35] *}

/// tip

The syntax `{"name", "description"}` creates a `set` with those two values.

It is equivalent to `set(["name", "description"])`.

///

#### Using `list`s instead of `set`s { #using-lists-instead-of-sets }

            //we're making an assumption that all <pre> elements contain java code
            //this should mostly be true :)
            //if it isn't true then the syntax highlighting won't spoil the view too much anyway
            newElement.setAttribute("language", "java");
            nodes.push(newElement);
            return true;
        }

        @Override

 * </tr>
 * <tr>
 * <td>{@link DateFormat#FULL} format without delimiters</td>
 * <td>{@literal HHmmss z}</td>
 * </tr>
 * <tr>
 * <td>Other</td>
 * <td>{@link Time#valueOf(String) JDBC escape syntax} format</td>
 * <td>{@literal HH:mm:ss}</td>
 * </tr>
 * </table>
 *
 * @author koichik
 * @see DateConversionUtil
 * @see TimestampConversionUtil
 */
public abstract class TimeConversionUtil {

 */
@SuppressWarnings("all")
public class srvsvc {

    /**
     * Private constructor to prevent instantiation.
     */
    private srvsvc() {
    }

    /**
     * Gets the RPC interface syntax string.
     * @return the interface UUID and version
     */
    public static String getSyntax() {
        return "4b324fc8-1670-01d3-1278-5a47bf6ee188:3.0";
    }

    /**

        if (input == null) {
            return StringUtil.EMPTY;
        }
        return input.toString().replaceAll(regex, replacement);
    }

    /**
     * Formats code content with syntax highlighting and line numbers.
     *
     * @param prefix the line number prefix pattern
     * @param style the CSS class name for styling
     * @param mimetype the MIME type of the content (currently unused)

      if (year in 70..99) year += 1900
      if (year in 0..69) year += 2000

      // If any partial is omitted or out of range, return -1. The date is impossible. Note that leap
      // seconds are not supported by this syntax.
      require(year >= 1601)
      require(month != -1)
      require(dayOfMonth in 1..31)
      require(hour in 0..23)
      require(minute in 0..59)
      require(second in 0..59)

among the schedulers for each pod. Documentation is [here](http://kubernetes.io/docs/admin/multiple-schedulers.md), design doc is [here](docs/proposals/multiple-schedulers.md).
  * More expressive node affinity syntax, and support for “soft” node affinity.
Node selectors (to constrain pods to schedule on a subset of nodes) now support

### Common Migration Issues

#### Issue: Import fails with "Invalid format"

**Solution**:
- Ensure NDJSON files have one valid JSON object per line
- Check for UTF-8 encoding
- Validate JSON syntax with `jq`:
  ```bash
  cat documents.ndjson | jq empty
  ```

#### Issue: GSA XML import creates no configurations

**Solution**:
- Verify XML structure matches GSA export format