Abstract: The present disclosure relates to systems, methods and computer readable media for evaluating performance of a machine learning system and providing one or more performance views representative of the determined performance. For example, systems disclosed herein may receive or identify performance information including outputs, accuracy data, and feature data associated with a plurality of test instances. In addition, systems disclosed herein may provide one or more performance views via a graphical user interface including graphical elements (e.g., interactive elements) and indications of accuracy data and other performance data with respect to feature clusters associated with select groupings of test instances from the plurality of test instances. The performance views may include interactive features to enable a user to view and intuitively understand performance of the machine learning system with respect to clustered groupings of test instances that share common characteristics.

Abstract: Implementations disclosed herein provide a targeted messaging service that interfaces with a targeted messaging client on a device. The targeted messaging service provides a user-specific package to the client that specifies which native controls to invoke in response to which triggering events, as well as the assets to deploy in the controls. The targeted messaging client, which runs in the context of the native application it is supporting, receives the package from the service and monitors for the events that trigger targeted messages. A targeted control is formed by an existing native control combined with a specific asset provided in the package. When a given event occurs, the targeted messaging client merges the asset with the native control and displays the resulting targeted control in a user interface to the application.

Abstract: Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata and may also include none, some, or all of the content of the represented remote file system objects. In response to a request to access content of a file system object represented by a placeholder, a client may obtain needed data from a remote storage system and stream or not stream the data to the requesting application based on whether the requesting application is capable of streaming the data.

Abstract: Implementations disclosed herein provide a targeted messaging service that interfaces with a targeted messaging client on a device. The targeted messaging service provides a user-specific package to the client that specifies which native controls to invoke in response to which triggering events, as well as the assets to deploy in the controls. The targeted messaging client, which runs in the context of the native application it is supporting, receives the package from the service and monitors for the events that trigger targeted messages. A targeted control is formed by an existing native control combined with a specific asset provided in the package. When a given event occurs, the targeted messaging client merges the asset with the native control and displays the resulting targeted control in a user interface to the application.

Abstract: Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata, searchable text, and may also include none, some, or all of the content of the represented remote file system objects. Search data from the placeholders is integrated into a local search database of the client such that the client is able to satisfy queries and identify relevant local and remote file system objects even when the client is offline with respect to remote storage.

Abstract: Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata and may also include none, some, or all of the content of the represented remote file system objects. In conjunction with local file system metadata, the placeholders allow a file system namespace to be navigated and may also allow other operations to be performed on the file system objects even when the client is offline with respect to the remote file system. After connectivity is re-established with the remote file system, the placeholders may be used in synchronizing changes.

Abstract: Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata and may also include none, some, or all of the content of the represented remote file system objects. In response to a request to access content of a file system object represented by a placeholder, a client may obtain needed data from a remote storage system and stream or not stream the data to the requesting application based on whether the requesting application is capable of streaming the data.

Abstract: Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata and may also include none, some, or all of the content of the represented remote file system objects. In response to a request to access content of a file system object represented by a placeholder, a client may obtain needed data from a remote storage system and stream or not stream the data to the requesting application based on whether the requesting application is capable of streaming the data.

Abstract: Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata, searchable text, and may also include none, some, or all of the content of the represented remote file system objects. Search data from the placeholders is integrated into a local search database of the client such that the client is able to satisfy queries and identify relevant local and remote file system objects even when the client is offline with respect to remote storage.

Abstract: Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata, searchable text, and may also include none, some, or all of the content of the represented remote file system objects. Search data from the placeholders is integrated into a local search database of the client such that the client is able to satisfy queries and identify relevant local and remote file system objects even when the client is offline with respect to remote storage.

Abstract: Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata and may also include none, some, or all of the content of the represented remote file system objects. In conjunction with placeholders and based on one or more factors, a client may hydrate or dehydrate file system objects of the client to follow user directives, inferred user intent, and storage policies of the client.

Abstract: Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata and may also include none, some, or all of the content of the represented remote file system objects. In response to a request to access content of a file system object represented by a placeholder, a client may obtain needed data from a remote storage system and stream or not stream the data to the requesting application based on whether the requesting application is capable of streaming the data.

Abstract: Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata and may also include none, some, or all of the content of the represented remote file system objects. In conjunction with local file system metadata, the placeholders allow a file system namespace to be navigated and may also allow other operations to be performed on the file system objects even when the client is offline with respect to the remote file system. After connectivity is re-established with the remote file system, the placeholders may be used in synchronizing changes.

Abstract: Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata and may also include none, some, or all of the content of the represented remote file system objects. In conjunction with placeholders and based on one or more factors, a client may hydrate or dehydrate file system objects of the client to follow user directives, inferred user intent, and storage policies of the client.

Abstract: Aspects of the subject matter described herein relate to file system placeholders. In aspects, placeholders may be used by a client to represent remote file system objects. The placeholders may include metadata, searchable text, and may also include none, some, or all of the content of the represented remote file system objects. Search data from the placeholders is integrated into a local search database of the client such that the client is able to satisfy queries and identify relevant local and remote file system objects even when the client is offline with respect to remote storage.

Abstract: Aspects of the subject matter described herein relate to a mechanism for seamlessly changing a network mode of a network device that is connected to multiple nodes. In aspects, agents reside on the nodes. A master agent communicates with the other agents and receives the capabilities of the nodes on which they execute. The master agent creates a data structure that includes the settings needed to connect using the new network mode. The master agent distributes this data structure to the other agents and each agent stores settings associated with the current network mode in case a rollback is needed. The master agent then instructs the other agents to begin communicating using the new network mode and the network device is reconfigured. If the master agent does not receive success acknowledgments from all of the other agents, the master agent initiates a rollback procedure.

Abstract: The claimed subject matter provides for systems and/or methods for accessing and/or updating files by a first application in which the first application does not have direct accessibility to said file. In some embodiments, file host applications that are not directly accessible to said first application may be connected to through a file picker extensibility point that enable the first application to acquire files through an operating system user experience. In these various embodiments, the system may provide for one or more of the following functionalities: (1) refreshing content that is controlled by a file host application; (2) updating content that is controlled by a file host application; (3) exporting files from an application to a file host application; (4) a user interface for export operations and file host application intervention and (5) a file host extensibility point provided by the operating system.

Abstract: Aspects of the subject matter described herein relate to a mechanism for seamlessly changing a network mode of a network device that is connected to multiple nodes. In aspects, agents reside on the nodes. A master agent communicates with the other agents and receives the capabilities of the nodes on which they execute. The master agent creates a data structure that includes the settings needed to connect using the new network mode. The master agent distributes this data structure to the other agents and each agent stores settings associated with the current network mode in case a rollback is needed. The master agent then instructs the other agents to begin communicating using the new network mode and the network device is reconfigured. If the master agent does not receive success acknowledgments from all of the other agents, the master agent initiates a rollback procedure.