context.put("key2", "value2");

        logger.logEvent(EventType.CONFIGURATION_CHANGE, Severity.INFO, "Configuration changed", context);

        Map<EventType, Long> stats = logger.getStatistics();
        assertEquals(Long.valueOf(1), stats.get(EventType.CONFIGURATION_CHANGE), "Should have 1 configuration event");
    }

    @Test
    @DisplayName("Test statistics accumulation")

     * @return the create request configured for reconnection
     */
    protected Smb2CreateRequest createReconnectionRequest(HandleInfo info) {
        // This would need access to the Configuration and proper setup
        // For now, we provide the structure

        // Smb2CreateRequest request = new Smb2CreateRequest(config, info.getPath());

        // configuration. We don't have an easy way to allow a pluggable builder to provide its own configuration
        // parameters but this is sufficient for now. Ultimately we want components like Builders to provide a way to
        // extend the command line to accept its own configuration parameters.
        //

 * This form is used in the admin interface to upload custom user dictionaries for Kuromoji.
 */
public class UploadForm {

    /**
     * The dictionary ID that identifies which Kuromoji dictionary configuration to update.
     * This ID corresponds to a specific Kuromoji dictionary instance in the system.
     */
    @Required
    public String dictId;

    /**

import org.gradle.api.file.DirectoryProperty;
import org.gradle.api.file.RegularFileProperty;
import org.gradle.api.provider.Property;

import java.net.URI;

/**
 * Configuration for generating Javadocs
 */
public abstract class Javadocs {
    /**
     * Link to Java API to use when generating Javadoc
     */
    public abstract Property<URI> getJavaApi();

    /**

  ~ See the License for the specific language governing permissions and
  ~ limitations under the License.
  -->
<!DOCTYPE module PUBLIC
        "-//Puppy Crawl//DTD Check Configuration 1.2//EN"
        "http://www.puppycrawl.com/dtds/configuration_1_2.dtd">
<module name="Checker">
    <module name="SuppressionFilter">
        <property name="file" value="${config_loc}/suppressions.xml"/>
    </module>

// along with this program.  If not, see <http://www.gnu.org/licenses/>.

package lambda

import "github.com/minio/minio/internal/event/target"

// Config - lambda target configuration structure, holds
// information about various lambda targets.
type Config struct {
	Webhook map[string]target.WebhookArgs `json:"webhook"`
}

const (
	defaultTarget = "1"
)

import jcifs.CIFSContext;
import jcifs.Configuration;
import jcifs.NameServiceClient;
import jcifs.NetbiosAddress;

/**
 * Test class for NTLMSSP Type 1 Message functionality
 */
@ExtendWith(MockitoExtension.class)
@DisplayName("Type1Message Tests")
class Type1MessageTest {

    @Mock
    private CIFSContext mockContext;

    @Mock
    private Configuration mockConfig;

    @Mock

Chart ---------- Install this chart using: ```bash helm install --namespace minio --set rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values...

 */
package jcifs.context;

import java.net.MalformedURLException;
import java.net.URLStreamHandler;

import jcifs.BufferCache;
import jcifs.CIFSContext;
import jcifs.CIFSException;
import jcifs.Configuration;
import jcifs.Credentials;
import jcifs.DfsResolver;
import jcifs.NameServiceClient;
import jcifs.SidResolver;
import jcifs.SmbPipeResource;
import jcifs.SmbResource;
import jcifs.SmbTransportPool;