public void clearHistory() {
            nameHistory.clear();
        }
    }

    private TestTransformer testTransformer;

    @Override
    protected void setUp() throws Exception {
        super.setUp();
        testTransformer = new TestTransformer();
    }

    /**
     * Test default constructor
     */
    public void test_constructor() {

import org.opensearch.search.sort.FieldSortBuilder;

public class CrawlingConfigHelperTest extends UnitFessTestCase {
    private CrawlingConfigHelper crawlingConfigHelper;

    @Override
    public void setUp() throws Exception {
        super.setUp();
        final File propFile = File.createTempFile("system", ".properties");
        propFile.deleteOnExit();
        FileUtil.writeBytes(propFile.getAbsolutePath(), "".getBytes());

import org.codelibs.fess.util.ComponentUtil;

public class WebFsIndexHelperTest extends UnitFessTestCase {

    private WebFsIndexHelper webFsIndexHelper;

    @Override
    public void setUp() throws Exception {
        super.setUp();
        webFsIndexHelper = new WebFsIndexHelper();
    }

    public void test_crawl_withNullParameters() {
        try {
            webFsIndexHelper.crawl("sessionId", null, null);

        response.setCommand(command);
        assertEquals(command, response.getCommand());

        // Test other setter methods
        doNothing().when(response).setUid(1000);
        response.setUid(1000);
        verify(response).setUid(1000);

        doNothing().when(response).setExtendedSecurity(true);
        response.setExtendedSecurity(true);
        verify(response).setExtendedSecurity(true);

This document explains how to setup Prometheus and configure it to scrape data from MinIO servers.

## Prerequisites

To get started with MinIO, refer [MinIO QuickStart Document](https://docs.min.io/community/minio-object-store/operations/deployments/baremetal-deploy-minio-on-redhat-linux.html).
Follow below steps to get started with MinIO monitoring using Prometheus.

### 1. Download Prometheus

    @Mock
    private CIFSContext context;

    @Mock
    private CommonServerMessageBlock disconnectRequest;

    @Mock
    private CommonServerMessageBlockRequest nextRequest;

    @BeforeEach
    void setUp() {
        // Reset mocks before each test
        reset(request, response, context, disconnectRequest, nextRequest);
    }

    @Test
    @DisplayName("Test initResponse returns initialized response")

        }

        public void setVerifyFailed(boolean verifyFailed) {
            this.verifyFailed = verifyFailed;
        }
    }

    @BeforeEach
    void setUp() {
        MockitoAnnotations.openMocks(this);

        // Setup mock notify information
        when(mockNotifyInfo1.getAction()).thenReturn(FileNotifyInformation.FILE_ACTION_ADDED);
        when(mockNotifyInfo1.getFileName()).thenReturn("test1.txt");

public class FessXpathTransformerTest extends UnitFessTestCase {
    private static final Logger logger = LogManager.getLogger(FessXpathTransformerTest.class);

    @Override
    public void setUp() throws Exception {
        super.setUp();
        ComponentUtil.register(new DataSerializer(), "dataSerializer");
    }

    public void test_transform() throws Exception {

The kube-scheduler is adding a new, simplified config field for Plugins to allow multiple extension points to be enabled in one spot.
The new `multiPoint` plugin field is intended to simplify most scheduler setups for administrators.
Plugins that are enabled via `multiPoint` will automatically be registered for each individual extension point that they implement.

RUN /build_devtoolset.sh devtoolset-9 /dt9

# Setup Python
COPY setup.python.sh /setup.python.sh
COPY builder.requirements.txt /builder.requirements.txt
RUN /setup.python.sh python3.9 /builder.requirements.txt
RUN /setup.python.sh python3.10 /builder.requirements.txt
RUN /setup.python.sh python3.11 /builder.requirements.txt
RUN /setup.python.sh python3.13 /builder.requirements.txt
RUN /setup.python.sh python3.13-nogil /builder.requirements.txt