{{- end }} minio/templates/_helper_policy.tpl {{- $statements_length := len .statements -}} {{- $statements_length := sub $statements_length 1 -}} { "Version": "2012-10-17", "Statement": [ {{- range $i, $statement := .statements }} { "Effect": "{{ $statement.effect | default "Allow" }}", "Action": [ "{{ $statement.actions | join "\",\n\"" }}" ]{{ if $statement.resources }}, "Resource": [ "{{ $statement.resources | join "\",\n\"" }}" ]{{ end }} {{- if $statement.conditions }} {{- $condition_len :=...

You could have turns as in the burgers example, first the living room, then the kitchen, but as you are not waiting 🕙 for anything, just cleaning and cleaning, the turns wouldn't affect anything.

It would take the same amount of time to finish with or without turns (concurrency) and you would have done the same amount of work.

	policyBytes := fmt.Appendf(nil, `{"Id": "Policy1637752602639", "Version": "2012-10-17", "Statement": [{"Sid": "Stmt1637752600730", "Action": "s3:DeleteObject", "Effect": "Allow", "Resource": "arn:aws:s3:::%s/public/*", "Principal": "*"}]}`, bucketName)
	rec := httptest.NewRecorder()

{{- end }} minio/templates/_helper_policy.tpl {{- $statements_length := len .statements -}} {{- $statements_length := sub $statements_length 1 -}} { "Version": "2012-10-17", "Statement": [ {{- range $i, $statement := .statements }} { "Effect": "{{ $statement.effect | default "Allow" }}", "Action": [ "{{ $statement.actions | join "\",\n\"" }}" ]{{ if $statement.resources }}, "Resource": [ "{{ $statement.resources | join "\",\n\"" }}" ]{{ end }} {{- if $statement.conditions }} {{- $condition_len :=...

   *
   * <p><b>Java 11+ users:</b> use {@link OutputStream#nullOutputStream()} instead. Note that the
   * {@link ByteStreams} method returns a singleton stream whose {@code close} method has no effect,
   * while the {@link OutputStream} method returns a new instance whose {@code write} methods throw
   * if called on a closed stream.
   *
   * @since 14.0 (since 1.0 as com.google.common.io.NullOutputStream)
   */

{
  "Version": "2012-10-17",
  "Statement": [
   {
    "Effect": "Allow",
    "Action": [
     "s3:*"
    ],
    "Resource": [
     "arn:aws:s3:::*"
    ]
   }
  ]

Go 1.23 re-enabled support in html/template for ECMAScript 6 template literals by default.
The [`jstmpllitinterp` setting](/pkg/html/template#hdr-Security_Model) no longer has
any effect.

Go 1.23 changed the default TLS cipher suites used by clients and servers when
not explicitly configured, removing 3DES cipher suites. The default can be reverted

 * for any {@link Object}. Also offers basic text processing methods based on this function.
 * Implementations are strongly encouraged to be side-effect-free and immutable.
 *
 * <p>Throughout the documentation of this class, the phrase "matching character" is used to mean
 * "any {@code char} value {@code c} for which {@code this.matches(c)} returns {@code true}".
 *

   * characters which constitute a machine-sensible address or routing information. Such a sequence
   * is referred to as the "heading." An STX character has the effect of terminating a heading.
   *
   * @since 8.0
   */
  public static final byte SOH = 1;

  /**
   * Start of Text: A communication control character which precedes a sequence of characters that

  It may affect some metrics values related to the `NodeAffinity` Filter plugin. ([#114125](https://github.com/kubernetes/kubernetes/pull/114125), [@sanposhiho](https://github.com/sanposhiho))
- Scheduler now skips `InterPodAffinity` Filter plugin when `InterPodAffinity` Filter plugin has nothing to do with a Pod.