package kms

import (
	"bytes"
	"sort"
	"unicode/utf8"
)

// Context is a set of key-value pairs that
// are associated with a generate data encryption
// key (DEK).
//
// A KMS implementation may bind the context to the
// generated DEK such that the same context must be
// provided when decrypting an encrypted DEK.
type Context map[string]string

// MarshalText returns a canonical text representation of

 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package gradlebuild.docs;

import org.gradle.internal.exceptions.Contextual;

@Contextual
public class DocGenerationException extends RuntimeException {
    public DocGenerationException(String message) {
        super(message);
    }

                new DERTaggedObject(true, 1, new ASN1Integer(14)), // msg-type
        });

        // Create CONTEXT tagged object instead of APPLICATION
        DERTaggedObject contextTag = new DERTaggedObject(false, 14, apReqSequence);

        // Build inner content with OID and magic bytes
        ByteArrayOutputStream innerContent = new ByteArrayOutputStream();

```jinja hl_lines="7"
{!../../docs_src/templates/templates/item.html!}
```

### Valeurs de contexte du template { #template-context-values }

Dans le HTML qui contient :

{% raw %}

```jinja
Item ID: {{ id }}
```

{% endraw %}

... il affichera l’`id` récupéré à partir du `dict` « context » que vous avez passé :

```Python
{"id": id}
```

Par exemple, avec un ID de `42`, cela rendrait :

        buf.enc_ndr_short(0); // auth length
        buf.enc_ndr_long(0); // call_id

        // Response body
        buf.enc_ndr_long(4); // alloc_hint
        buf.enc_ndr_short(0); // context_id
        buf.enc_ndr_short(0); // cancel_count
        buf.enc_ndr_small(0xAB); // test data for decode_out

        // Decode
        buf.setIndex(0);
        TestMessage m = new TestMessage();

 * application-specific data to provide context when invoking session methods.</p>
 *
 * <p>This trace information is particularly useful for:</p>
 * <ul>
 *   <li>Debugging and troubleshooting request flows</li>
 *   <li>Audit logging of session operations</li>
 *   <li>Performance monitoring of nested operations</li>
 * </ul>
 *

def test_dependency_contextvars():
    """
    Check that custom middlewares don't affect the contextvar context for dependencies.

    The code before yield and the code after yield should be run in the same contextvar
    context, so that request_state_context_var.reset(contextvar_token).

    If they are run in a different context, that raises an error.
    """
    response = client.get("/user")
    assert response.json() == "deadpond"

 */
package jcifs;

import java.net.URLStreamHandler;

/**
 * Encapsulation of client context
 *
 *
 * A context holds the client configuration, shared services as well as the active credentials.
 *
 * Usually you will want to create one context per client configuration and then
 * multiple sub-contexts using different credentials (if necessary).
 *

  // Set up distributed execution environment on local and remote tasks.
  // When `reset_context` is true, initialize new cluster context state based
  // on cluster configurations provided in `server_def`; otherwise, update
  // existing context state with the provided `server_def`. Contexts created
  // on remote tasks will be considered stale and garbage collected after
  // `keep_alive_secs` of inactivity.

 * irrespective of if they are direct dependencies or transitive ones ( that should be children of other children ).
 * Although we end up lacking some contextual information, this allows us to scan and monitor only the dependencies
 * that are bundled and used in runtime.
 */
public class DependenciesGraphTask extends DefaultTask {

    private Configuration runtimeConfiguration;