//
// We expose this here to allow fine-grained synchronization in multi-threaded
// workloads, which is required since the Python implementation depends on the
// above mutation methods. This allows us to prevent modifications to nodes in
// the graph after the session has been made aware of them.
TF_CAPI_EXPORT extern void TF_ExtendSession(TF_Session* session,
                                            TF_Status* status);

        .build(),
    )

    // At least three request/response pairs are required because after the first request is cached
    // a different execution path might be taken. Thus modifications to the cache applied during
    // the second request might not be visible until another request is performed.
    assertThat(get(server.url("/")).body.string()).isEqualTo("ABCABCABC")

          <type>String</type>
          <description>The mechanism used to deliver notifications.</description>
        </field>
        <field>
          <name>sendOnError</name>
          <version>4.0.0+</version>
          <defaultValue>true</defaultValue>
          <type>boolean</type>
          <description>Whether to send notifications on error.</description>
        </field>
        <field>

 * about file system changes such as file creation, deletion, or modification events.
 *
 * @author mbechler
 */
public interface NotifyResponse extends CommonServerMessageBlockResponse {

    /**
     * Gets the file notification information from the response.
     * @return notify information containing file change notifications
     */
    List<FileNotifyInformation> getNotifyInformation();

import jcifs.internal.SMBProtocolDecodingException;

/**
 * Response for SMB1 NT Transaction change notification.
 *
 * This response contains file system change notifications that occurred
 * in the monitored directory, such as file creation, modification, or deletion.
 */
public class NtTransNotifyChangeResponse extends SmbComNtTransactionResponse implements NotifyResponse {

	"github.com/minio/minio/internal/auth"
	"github.com/minio/minio/internal/hash/sha256"
	xhttp "github.com/minio/minio/internal/http"
	ioutilx "github.com/minio/minio/internal/ioutil"
)

// Type to capture different modifications to API request to simulate failure cases.
type Fault int

const (
	None Fault = iota
	MissingContentLength
	TooBigObject
	TooBigDecodedLength
	BadSignature
	BadMD5
	MissingUploadID
)

To disable replica metadata modification syncing, use `mc replicate edit` with the --replicate flag.

```
mc replicate edit alias/bucket --id xyz.id --replicate "delete,delete-marker"
```

To re-enable replica metadata modification syncing,

```
mc replicate edit alias/bucket --id xyz.id --replicate "delete,delete-marker,replica-metadata-sync"

        // Verify first notification
        assertEquals("file1.txt", notifications.get(0).getFileName());
        assertEquals(FileNotifyInformation.FILE_ACTION_ADDED, notifications.get(0).getAction());

        // Verify second notification
        assertEquals("file2.txt", notifications.get(1).getFileName());
        assertEquals(FileNotifyInformation.FILE_ACTION_REMOVED, notifications.get(1).getAction());

        // Verify third notification

        List<FileNotifyInformation> notifications = response.getNotifyInformation();
        assertEquals(3, notifications.size());

        assertEquals(1, notifications.get(0).getAction());
        assertEquals("file1", notifications.get(0).getFileName());

        assertEquals(2, notifications.get(1).getAction());
        assertEquals("file2", notifications.get(1).getFileName());

### kubeadm

* kubeadm: Modifications to cluster-internal resources installed by kubeadm will be overwritten when upgrading from v1.6 to v1.7. ([#47081](https://github.com/kubernetes/kubernetes/pull/47081), [@luxas](https://github.com/luxas))