*/
package jcifs.internal;

import java.util.List;

import jcifs.FileNotifyInformation;

/**
 * Interface for SMB change notification response messages.
 * Handles responses from directory change notification requests, providing information
 * about file system changes such as file creation, deletion, or modification events.
 *
 * @author mbechler
 */

  "durations" : [ {
    "testProject" : "largeJavaMultiProject",
    "linux" : 942
  } ]
}, {
  "scenario" : "org.gradle.performance.regression.buildcache.TaskOutputCachingJavaPerformanceTest.clean assemble for non-abi change with local cache",
  "durations" : [ {
    "testProject" : "largeJavaMultiProject",

alogs.removeInputStylingAndMessage(f,c)})};b.find("[data-validation-depends-on]").off("beforeValidation",d).on("beforeValidation",d).each(function(){var c=a(this);b.find('[name="'+c.valAttr("depends-on")+'"]').each(function(){a(this).off("change",f).on("change",f).valAttr("depending-value",c.valAttr("depends-on-value")),this.dependingInputs=this.dependingInputs||[],this.dependingInputs.push(c)})})},c=function(b,c){var d=function(){var c=a(this),d=c.valAttr("optional-if-answered"),e=!1,f=!!a.form...

        description =
            "Promotes the latest successful changes on '${branch.branchName}' from Ready for Nightly as a new nightly snapshot"

        triggers {
            val triggerHour = branch.determineNightlyPromotionTriggerHour() ?: return@triggers
            // for master/release branch, we trigger them on midnight (with pending change only, i.e. if there is no change, don't rigger it)

        params {
            text(
                "gitUserEmail",
                "",
                label = "Git user.email Configuration",
                description = "Enter the git 'user.email' configuration to commit change under",
                display = ParameterDisplay.PROMPT,
                allowEmpty = true,
            )
            text(
                "confirmationCode",
                "",

name: Go Telemetry Proposals
description: Changes to the telemetry upload configuration
title: "x/telemetry/config: proposal title"
labels: ["Telemetry-Proposal"]
projects: ["golang/29"]
body:
- type: textarea
  attributes:
    label: Summary
    description: >
      What change are you proposing to the upload configuration, and why?
      For new upload configuration, which new counters will be collected, what

<img src="/img/tutorial/extending-openapi/image03.png">

## Change the Theme { #change-the-theme }

The same way you could set the syntax highlighting theme with the key `"syntaxHighlight.theme"` (notice that it has a dot in the middle):

{* ../../docs_src/configure_swagger_ui/tutorial002_py310.py hl[3] *}

That configuration would change the syntax highlighting color theme:

* path operation function: função de operação de rota
* prefix: prefixo
* request (as in HTTP request): request (do not change if it's already translated to requisição)
* router (as in FastAPI's router): router (do not change if it's already translated to "roteador" or "roteadores")
* response (as in HTTP response): response (do not change if it's already translated to resposta)
* shutdown (of the app): encerramento

## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->

## Current Behavior
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
<!--- If suggesting a change/improvement, explain the difference from current behavior -->

## Possible Solution

- Root credentials can now be changed easily. Before, a two-step process was required to
   change the cluster root credentials since they were used to en/decrypt the IAM data.
   So, both - the old and new credentials - had to be present at the same time during a rotation
   and the old credentials had to be removed once the rotation completed. This process is now gone.
   The root credentials can now be changed easily.