Abstract: Disclosed are various embodiments for tracking developer behavior with respect to software analysis tools. In one embodiment, a security analysis is performed upon a first revision of a program, where the security analysis is based at least in part on a plurality of rules. A first security issue found in the security analysis upon the first revision of the program is identified. The security analysis is performed upon a second revision of the program. A second security issue found in the security analysis upon the second revision of the program is identified. The rules are updated based at least in part on whether the first security issue is corrected in the second revision as determined based at least in part on a comparison of the first security issue to the second security issue.

Abstract: This document describes techniques for placing instances on servers of a service provider environment. In an example embodiment, a system can determine that characteristics of a new virtual machine instance match a co-tenant policy of an existing virtual machine instance on a server and factor that information into a decision to place the virtual machine instance.

Abstract: Disclosed are various embodiments for tracking developer behavior with respect to software analysis tools. In one embodiment, a security analysis is performed upon a first revision of a program, where the security analysis is based at least in part on a plurality of rules. A first security issue found in the security analysis upon the first revision of the program is identified. The security analysis is performed upon a second revision of the program. A second security issue found in the security analysis upon the second revision of the program is identified. The rules are updated based at least in part on whether the first security issue is corrected in the second revision as determined based at least in part on a comparison of the first security issue to the second security issue.

Abstract: Disclosed are various embodiments for identifying characteristics of developers of problematic software. Report data generated by a security analysis tool is received, which is based at least in part on a security analysis of a program or an operational configuration. The report data indicates one or more security issues identified in the program or the operational configuration. A user is identified who is responsible for at least a threshold impact of the security issue(s). Coding or configuration characteristics associated with the user are then determined.

Abstract: Techniques for determining whether data associated with an autonomous/non-autonomous operation of a manned/unmanned vehicle may be trusted. For example, a first set of data may be provided from a source external to a manned/unmanned vehicle. A second set of data may be accessed. This second set may be provided from a source internal or external to the manned/unmanned vehicle and may be associated with the same autonomous/non-autonomous operation. The two sets may be compared to determine whether the first set of data may be trusted or not. If untrusted, a corrective action may be performed.

Abstract: Described are techniques for outputting or suppressing output of network content to a user device based on content previously accessed by the user device. Correspondence between network content accessed by the user device and spoiler data determined from media content may indicate that the network content is associated with the media content. Content consumption data associated with the user device may indicate whether the user device has previously accessed the media content. The network content may be suppressed from output if the user device has not previously accessed the media content. The network content may be output to the user device if the media content has been accessed.

Abstract: The present disclosure describes a system and method that identifies locations in source code files that are associated with particular Web requests. The system generates a fingerprint for each Web request based at least in part on the parameters of each HTTP request. By fingerprinting the properties of the source code that generates each HTTP request, Web requests that are generated by executing the fingerprinted code can be traced back to specific source code files, and in some cases an exact line of code. In many examples, a webpage or an action on a webpage can be traced back to a line of source code that is associated with the request. This may allow a developer to find a software defect or security vulnerability by tracing Web requests of a running application and then mapping suspect Web requests back to corresponding lines of code.

Abstract: This disclosure describes systems and processes using multirotor lifter to deploy and/or engage fixed wing aircraft. For example, one or more unmanned multirotor lifters may engage an unmanned fixed wing aircraft, aerially navigate the fixed wing aircraft vertically to a desired altitude, and then release the fixed wing aircraft so that the fixed wing aircraft can initiate a flight plan. In some implementations, multirotor lifter may also be configured to engage fixed wing aircraft while both the multirotor lifters and the fixed wing aircraft are in flight.

Abstract: A non-transitory computer-readable storage device stores instructions that, when executed on a computing system, cause the computing system to receive a request for creating a new software container and determine that characteristics of the new software container match a co-tenant policy of an existing software container on a server. The instructions further cause the computing system to determine that characteristics of the existing software container match a co-tenant policy of the new software container as well as cause the new software container to be created on the server.

Abstract: The present disclosure describes a system and method that identifies locations in source code files that are associated with particular Web requests. The system generates a fingerprint for each Web request based at least in part on the parameters of each HTTP request. By fingerprinting the properties of the source code that generates each HTTP request, Web requests that are generated by executing the fingerprinted code can be traced back to specific source code files, and in some cases an exact line of code. In many examples, a webpage or an action on a webpage can be traced back to a line of source code that is associated with the request. This may allow a developer to find a software defect or security vulnerability by tracing Web requests of a running application and then mapping suspect Web requests back to corresponding lines of code.

Abstract: Techniques for determining whether data associated with an autonomous operation of an unmanned vehicle may be trusted. For example, a first set of data may be provided from a source external to the unmanned vehicle. A second set of data may be accessed. This second set may be provided from a source internal to the unmanned vehicle and may be associated with the same autonomous operation. The two sets may be compared to determine whether the first set of data may be trusted or not. If untrusted, the autonomous navigation may be directed based on the second set of data and independently of the first set.

Abstract: Techniques for determining whether data associated with an autonomous operation of a first unmanned vehicle may be trusted. For example, the first unmanned vehicle may receive an indication related to the data and originating from a second unmanned vehicle over a network. For instance, the indication may indicate that similar data for a similar autonomous operation of the second unmanned vehicle may be untrusted. Based on a level of trust accorded to the indication, the first unmanned vehicle may determine that the data may be untrusted and the autonomous navigation may be directed independently of the data.

Abstract: Described are techniques for associating messages with a particular portion of media content. A message received from a first device, associated with a portion of media content stored on the first device, may be provided to a second device and stored in association with a corresponding portion of media content on the second device. Content consumption data associated with the second device may indicate whether the second device has previously accessed the portion of the media content. The message may be suppressed from presentation if the second device has not previously accessed the corresponding portion of the media content. The message may be presented to the second device when the corresponding portion of the media content is accessed.

Abstract: The subject technology provides embodiments for providing an index of source code repositories isolated to HTTP request parameters. By fingerprinting specific actions involving HTTP requests, such actions can be traced to specific source code files, and in some cases an exact line of code. The end result is that a webpage and any action on that webpage can be traced back to the exact line of source code that is accepting that request. This will allow the ability to find a software defect or security vulnerability while looking at a running application and then map it back directly to the line of code that needs to be modified.

Abstract: Disclosed are various embodiments for identifying characteristics of developers of problematic software. Report data generated by a security analysis tool is received, which is based at least in part on a security analysis of a program or an operational configuration. The report data indicates one or more security issues identified in the program or the operational configuration. A user is identified who is responsible for at least a threshold impact of the security issue(s). Coding or configuration characteristics associated with the user are then determined.

Abstract: Techniques for determining whether data associated with an autonomous operation of an unmanned vehicle may be trusted. For example, the data may be analyzed in light of a capability of the unmanned vehicle. The analysis may indicate an operation of the unmanned vehicle. If the operation is unsupported by the capability, the data may be determined to be untrusted. Accordingly, the autonomous navigation may be directed independently of the untrusted data.

Abstract: Disclosed are various embodiments for tracking developer behavior with respect to software analysis tools. In a first embodiment, issues with a first revision of a program are identified with an analysis tool. The configuration of the analysis tool may be updated based at least in part on a status of the issues in the second revision of the program. In a second embodiment, an analysis tool identifies issues with a program. A developer responsible for the issues is identified. A coding characteristic associated with the developer is then determined.

Abstract: Techniques for determining whether data associated with an autonomous navigation of an unmanned vehicle may be trusted. For example, navigation-related data may be provided from a source external to the unmanned vehicle. Image data associated with the autonomous navigation may be generated. The navigation-related data and the image data may be compared to determine whether the navigation data may be trusted or not. If untrusted, the autonomous navigation may be directed independently of the navigation data.

Abstract: This disclosure describes systems and processes using multirotor lifter to deploy and/or engage fixed wing aircraft. For example, one or more unmanned multirotor lifters may engage an unmanned fixed wing aircraft, aerially navigate the fixed wing aircraft vertically to a desired altitude, and then release the fixed wing aircraft so that the fixed wing aircraft can initiate a flight plan. In some implementations, multirotor lifter may also be configured to engage fixed wing aircraft while both the multirotor lifters and the fixed wing aircraft are in flight.

Abstract: Techniques are described for automatically determining application composition and application ownership of an application that may include a plurality of files deployed to a plurality of host devices. The determination of application composition may be based on analyzing various types of metadata that may provide evidence of associations between deployed files, such as metadata describing the deployment of files to host devices, metadata describing the files tracked within a source control system, or other types of metadata. The determination of application ownership may also be based on analyzing the various types of metadata that provide evidence of associations between files and individuals or groups of individuals within an organization.