Abstract: Data is received or accessed that includes a structured file encapsulating data required by an execution environment to manage executable code wrapped within the structured file. Thereafter, code and data regions are iteratively identified in the structured file. Such identification is analyzed so that at least one feature can be extracted from the structured file. Related apparatus, systems, techniques and articles are also described.

Abstract: An example system and method facilitates developing and interacting with connectors that represent or are associated with services or interfaces to be implemented in a computing environment. The example system includes a connector editor backed by a connectors framework that specializes and links to the specific editor and dialogs that enables a developer to customize and configure any of plural available connectors for a specific purpose (e.g., to connect a process step to a particular type of web service). Furthermore, the connectors framework and associated editor(s) enable all of the connectors of available connector types to be configured using the same life cycle and to be automatically parameterized to use different data when running on the different environments, e.g., different test and production environments.

Abstract: Techniques for simplifying the process of building an application and making changes to the application. The process of creating and editing an application is simplified such that a non-technical user can build and edit applications without having any programming or technical knowledge. An infrastructure is provided for building an application that enables a user to create an application by simply designing a user interface for the application using one or more provided user interface (UI) components. A user can build a full executable application by simply using UI components and the back end data objects and schemas used for the application are automatically created and updated by the infrastructure. Due to the automatic creation of the data objects and schemas and the automatic binding of these to the UI components of the application, the application being built is able to run or execute while being built and/or edited.

Abstract: Systems and methods improve performance and resource-efficiency of Just-in-Time (JIT) compilation in a hypervisor-based virtualized computing environment. A user attempts to launch an application that has been previously compiled by a JIT compiler into an intermediate, platform-independent format. A JIT accelerator selects a unique function signature that identifies the application and the user's target platform. If the signature cannot be found in a repository, indicating that the application has never been run on the target platform, the accelerator generates and stores the requested executable program in shared memory and saves the signature in the repository. The system then returns to the user a pointer to the stored platform-specific executable. If multiple users of the same platform request the same application, the system recognizes an affinity among those requests identified by their shared signature, and provides each user a pointer to the same previously stored, shared executable.

Abstract: Disclosed herein are representative embodiments of tools and techniques for installing, executing, and/or updating managed applications through generation of native code from code in an intermediate language. According to one exemplary technique, a computing device receives machine dependent intermediate language code (MDIL code) generated by an online provider for an application. Additionally, the computing device installs the application on the computing device by generating a native image for the application, which includes binding a portion of the MDIL code with one or more libraries on the computing device. Also, the native image is stored on the computing device for use in loading the application for execution.

Abstract: Dynamically revising an in-process build is disclosed. A build system receives a build configuration comprising information that defines a plurality of successive stages. Each stage includes at least one step, and one or more of the stages include a plurality of successive steps. The build configuration defines a build process that, when completed, alters a state of a storage device. The build system initiates a build process sequence on the build configuration. The build system, after initiating the build process sequence, receives notification of a desire to add a revision to a particular stage of the plurality of stages defined in the build configuration. A determination is made that performance of the particular stage has or has not begun. In response to the determination, a subsequent build process action is performed.

Abstract: In accordance with disclosed embodiments, there are provided systems, methods, and apparatuses for implementing schema-driven on-the-fly code generation within a cloud based computing environment.

Abstract: A system comprising at least one computer hardware processor configured to perform: generating an object hierarchy comprising a plurality of objects corresponding to active graphical user interface (GUI) elements of at least one application program; controlling the at least one application program to perform a task comprising a sequence of actions at least in part by using the object hierarchy to invoke actions in the sequence of actions.

Abstract: Information concerning software bugs including bug detection, bug prediction data and/or historical bug data can be used to determine whether it is safe to commit, integrate, deploy and/or deliver a software change. If the change is deemed unsafe, the change can be rejected automatically. Alternatively, the change can proceed following approval by an administrator, supervisor, implementer, manager and/or other designated approval mechanism. Actions taken to override a block can be recorded along with information concerning failed deployments and/or deliveries, a higher than normal customer failure rate after deployment and/or delivery or through manual data entry.

Abstract: The present disclosure discloses method and automated exploratory testing system for performing automated exploratory testing of software applications. The automated exploratory testing system receives test application and data associated with test application, from data sources. The data comprises environment information and goal information. The system identifies defects in components of test application along with corresponding reward value, by performing a plurality of actions on each of components. The plurality of actions is determined based on a predefined machine learning technique and data. The system determines test strategy, by analysing components with defects, plurality of actions corresponding to defects, corresponding reward value and historic test data associated with other applications related to test application.

Abstract: Systems, methods, and apparatuses are provided for code injection and code interception in an operating systems having multiple subsystem environments. Code injection into a target process can rely on generation of a virtual process that can permit analysis of information loaded in a memory image of the target process regardless of the host environment in which the target process is executed. Based at least on information collected via the analysis, code can be injected into the target process while preserving integrity of the target process. Code interception also can exploit the analysis for suitable hooking that preserves integrity of target process. Code interception can utilize relocatable tokenized code that can be parameterized through token replacement.

Abstract: Information concerning software bugs including bug detection, bug prediction data and/or historical bug data can be used to determine whether it is safe to commit, integrate, deploy and/or deliver a software change. If the change is deemed unsafe, the change can be rejected automatically. Alternatively, the change can proceed following approval by an administrator, supervisor, implementer, manager and/or other designated approval mechanism. Actions taken to override a block can be recorded along with information concerning failed deployments and/or deliveries, a higher than normal customer failure rate after deployment and/or delivery or through manual data entry.

Abstract: Disclosed are systems, methods, and articles for determining compatibility of a mobile application and operating system on a mobile device. In some aspects, a method includes receiving one or more data values from a mobile device having a mobile medical software application installed thereon, the data value(s) characterizing a version of the software application, a version of an operating system installed on the mobile device, and one or more attributes of the mobile device; determining whether the mobile medical software application is compatible with the operating system by at least comparing the received data value(s) to one or more test values in a configuration file; and sending a message to the mobile device based on the determining, the message causing the software application to operate in one or more of a normal mode, a safe mode, and a non-operational mode.

Abstract: Techniques that facilitate group patching recommendation and/or remediation with risk assessment are provided. In one example, a system includes a vertical stack component, a horizontal stack component and a risk classification component. The vertical stack component identifies a first patch profile from a software system associated with a computer system environment. The horizontal stack component identifies a second patch profile from a hardware system associated with network nodes of the computer system environment. The system learns over time to identify repetitive patterns using machine learning techniques. Then, the risk classification component performs a machine learning process to determine a risk classification for the computer system environment based on the first patch profile and the second patch profile.

Abstract: A deployment subsystem provides updates to an application and/or software executed by server computer systems. The update is included in an update script. Execution of the update script by a server computer system causes the server computer system to execute a set of checks. After completing the set of checks the server computer system may execute the update to the application and/or software executed by server computer systems.

Abstract: Methods and apparatus for software lifecycle management of a virtual computing environment are disclosed. An example method includes determining, by executing an instruction with a processor, a plurality of software updates to be installed on physical computing resources in the virtual server rack system, the determining based on a manifest file received from a software manager associated with the virtual server rack system, determining, by executing an instruction with the processor, dependency requirements for installing the software updates identified in the manifest file, determining, by executing an instruction with the processor, an order for installation of the software updates to meet dependency requirements, and scheduling, by executing an instruction with the processor, installation of the software updates identified in the manifest file.

Abstract: In one embodiment, an integrated development environment (IDE) is maintained on a computing device for managing software code for one or more software programs. At the IDE on the computing device, one or more code changes to the software code are determined between a given version of the software code and a subsequent version of the software code, and then a performance impact of each of the one or more code changes is determined. The IDE (or IDE plugin) prepares user-understandable indications of the performance impact of the one or more code changes, and displays the user-understandable indications of the performance impact in a graphical user interface (GUI) when a respective code change is displayed in the GUI.

Abstract: Techniques to preprocess tensor operations prior to code generation to optimize compilation are disclosed. A computer readable representation of a linear algebra or tensor operation is received. A code transformation software component performs transformations include output reduction and fraction removal. The result is a set of linear equations of a single variable with integer coefficients. Such a set lends itself to more efficient code generation during compilation by a code generation software component. Use cases disclosed include targeting a machine learning hardware accelerator, receiving code in the form of an intermediate language generated by a cross-compiler with multiple front ends supporting multiple programming languages, and cloud deployment and execution scenarios.

Abstract: For each detected bug, historical code with similar characteristics and bug corrections from a historical bug dataset can be displayed in a source code editor. Relevant training and/or testing data can be found by comparing an internal representation of the code under development with an internal representation of the original buggy code in the historical bug dataset. Training and/or testing data that is relevant to the current code can be distinguished from irrelevant training and/or testing data by determining that the code syntax tokens from the current and historical data overlap to at least a specified percentage. Code can be devolved into a set of metrics. The degree of overlap between the metric sets can be determined. If a computed risk factor for the bug correction meets or exceeds a specified threshold, the bug correction can be automatically applied. Additional testing can be automatically performed on and/or added to the corrected code.

Abstract: Tentatively executing an entity includes performing a first, execution of an entity. At a point in the first execution, the first execution is suspended and input specifying an alternate value for a runtime data element is received. Based on the input, a second execution of the entity is performed starting at the point in the first execution, while enabling the first execution to be later resumed unaffected by the second execution. This second execution includes setting the runtime data element to the alternate value, and emulating one or more memory writes performed by the entity during the second execution. The first execution of the entity could comprise a live execution, an execution that is based on trace data, an execution based on a process dump, etc.