Abstract: A computing system including a first and a second application. The first application includes a first local software development kit (SDK) platform instance, and the first local SDK platform instance includes a first non-core SDK module instance, an application discovery module, and an inter-application communication module. The second application includes a second local SDK platform instance. The first non-core SDK module instance is configured to is a request to the application discovery module. Upon receipt of the request, the discovery module is configured to determine that the second local SDK platform instance includes a second non-core SDK module instance that is configured to service the request. The first local SDK platform instance, based on the determination, is configured to generate a deep link associated with the second application based on data collected by the first local SDK platform instance and provide the deep link to the first non-core SDK module.

Abstract: According to one embodiment of the present disclosure, a computing system is provided, including a graphical processing unit (GPU) and a processor. The processor may be configured to execute a run-time executable cross-compiler to receive a GPU-executed program of a plurality of GPU-executed programs. The processor may be further configured to receive summary data associated with the GPU-executed program. The summary data may include a sequence in which the plurality of GPU-executed programs are configured to be executed. Based at least in part on the GPU-executed program and the summary data, the processor may be further configured to generate a translated GPU-executed program.

Abstract: This disclosure describes techniques for providing users of services provided by network-based service platforms with additional control for approving patches that are to be deployed to computing resources that support their services. In some examples, the techniques include generating and using a “snapshot,” or list, of patches that are preliminarily approved for deployment. Prior to deploying the patches to the computing resources, users are provided with access to the snapshot and are able to modify the snapshot. For example, users can modify the snapshot by adding patches, removing patches, specifying a sequence in which the patches are to be deployed, and so forth. The snapshot of patches may be “frozen” for a period of time, meaning that patches that during the period of time, only patches in the snapshot are deployed, and patches that are not included in the snapshot are not permitted to be deployed to computing resources.

Abstract: Techniques are described herein that are capable of modeling a lifetime of a hybrid software application using an application manifest. For instance, workflows and input-output information may be received (e.g., from an independent software vendor). The workflows are configured to implement respective heterogeneous software products that are included in a hybrid software application. The input-output information specifies inputs of the heterogeneous software products and a mapping between output(s) of first heterogeneous software product(s) and input(s) of second heterogeneous software product(s). Operations that are to be performed to execute the workflows are determined based at least in part on the inputs and the mapping. A lifetime of the hybrid software application is modeled by generating an application manifest that defines the lifetime based at least in part on the operations.

Abstract: Production or development uses of an application may be identified from tracing data when the data fits a heuristic. The heuristic may include length of execution run, number of executions, repeating patterns within the execution run, or other factors. Similarly, prototyping or development uses of an application may be identified by frequent code changes, sporadic uses, low loads, and other factors. The production and development uses of an application may be displayed by a uses versus user graph, where production users may be displayed as those users with the largest number of uses. The tracing data may be gathered by monitoring an entire application or from monitoring functions, modules, subroutines, libraries, interfaces, services, or other portions of an application.

Abstract: A computing device for just-in-time cross-compiling compiled binaries of application programs that utilize graphics processing unit (GPU) executed programs configured to be executed on a first GPU having a first application binary interface (ABI) including a second GPU having a second ABI different from the first ABI of the first GPU, and a processor configured to execute an application program that utilizes a plurality of GPU-executed programs configured to be executed for the first ABI of the first GPU, execute a run-time executable cross-compiler configured to, while the application program is being executed, emulate the first ABI using hardware resources of the second GPU by translating between the first ABI and the second ABI, and execute the plurality of GPU-executed programs on the second GPU with the emulated first ABI, and pass output of the plurality of GPU-executed programs for the emulated first ABI through the second ABI.

Abstract: A system (100) includes an update server (110) in communication with one or more client devices (106,107,108) across a network (102). A smart scheduler engine (118) schedules deployment of an update (117) to at least a first group of client devices. A monitoring auto configuration server interface (111) deploys the update to the first group of client devices. An analytics engine (114) identifies one or more anomalies occurring in the first group of client devices resulting from the upgrade. When this occurs, the scheduling engine cancels future updates to at least a second group of client devices where the later group includes devices having one or more device characteristics that correlate with other devices of the first group of client devices experiencing the one or more anomalies.

Abstract: Configuration utilities, such as object wizards, enable automatic configuration of domain-specific assets from object templates based on domain specific options. In an aspect, an application object template library stores a set of previously defined application object templates. The templates each include a superset of options common to a set of related domain objects. A configuration utility is configured for specifying at least one domain-specific option of the superset and creating an application object instance to be included in an application. The application object instance comprising at least one of the application object templates having the specified domain-specific option.

Abstract: A system for providing a computer configured to read an immutable value for a variable; read the value of the variable at a specific timestamp, thereby providing an ability to create looping constructs; set a current or next value of a loop variable as a function of previous or current loop variables; read a set of all values that a variable will assume; push or scatter the values into collections; reduce the collections into a single value; display graphical node representations to indicate computed values next to corresponding source code lines in an editor, and edge representations to indicate dependencies between values; visualize data output by a given node; permit the user to reorder source code lines by dragging nodes; cache or memoize computed values, and reuse cached or memoized values to implement reactive programming, minimizing recomputation in response to changes to program or data.

Abstract: A compilation system can apply a smoothness constraint to the arguments of a compute-bound function invoked in a software program, to ensure that the value(s) of one or more function arguments are within specified respective threshold(s) from selected nominal value(s). If the constraint is satisfied, the function invocation is replaced with an approximation thereof. The smoothness constraint may be determined for a range of value(s) of function argument(s) so as to determine a neighborhood within which the function can be replaced with an approximation thereof. The replacement of the function with an approximation thereof can facilitate simultaneous optimization of computation accuracy, performance, and energy/power consumption.

Abstract: A method of upgrading firmware of an adapter includes transmitting a set of n data blocks of first upgrade file to the adapter, receiving a first response information of the adapter based on the set of n data blocks, and determining that the updating procedure of the adapter fails when the first response information indicates that the adapter fails to receive all of the n data blocks. In the method, a mobile terminal transmits the upgrade file to the adapter and the adapter sends determination information to the mobile terminal after the adapter receives the upgrade file having a predetermined size. In a time interval, if the mobile terminal fails to receive the determination information or the adapter does not receive the upgrade file, the upgrading firmware of the adapter fails.

Abstract: A method for agent-based transaction analysis which includes: building an instrumented binary code of a software application for a transaction; configuring an analysis agent for the software application; starting the software application in an application process environment with the instrumented binary code; attaching the analysis agent to the instrumented binary code of the software application; extracting by the analysis agent the metadata from the software application; sending the metadata to a central analysis server in an environment separate from the application process environment; and building by the central analysis server an end-to-end description of the transaction from the metadata.

Abstract: Multiphased profile guided optimization optimizes executable code based on data collected during multiple training runs of a training executable. In multiphased profile guided optimization, multiple sets of profiling data are collected where each set of profiling data is associated with a program phase and a particular training run. Program phases include but are not limited to different program features, startup, steady state and shutdown. The program features can run concurrently. Priority of the phases can be specified.

Abstract: The present disclosure relates to autogenic software testing. In some embodiments, a method of the present disclosure includes scanning source code to identify one or more methods to be tested. The method further includes generating one or more test cases which perform requests using the one or more methods. The method further includes generating one or more logs comprising results of the requests. The method further includes scanning the one or more logs to identify a pattern associated with a request. The method further includes determining that the pattern is not stored in a test data store. The method further includes generating a first test and a first expected response based on the pattern. The method further includes storing the first test and the first expected response in the test data store. The first test may be executed and evaluated based on the first expected response.

Abstract: A pre-initialized value of contents of a memory location is identified. A load value of contents loaded from the memory location by execution of a first instruction that loads from the memory location is also identified. A comparison is made between the load value and the pre-initialized value. Based on the comparison, a determination is made that the load value and the pre-initialized value are the same. In response to this determination, it is indicated that the first instruction contains an uninitialized memory reference.

Abstract: Data structures, methods, program products and systems for creating and executing an executable file for the Binary Runtime Environment for Wireless (BREW) where the file is capable of causing presentation of a document embedded in the file on a BREW system.

Abstract: Methods and apparatuses are described for automated generation and execution of computer software test cases. A digitized voice segment is captured that corresponds to speech submitted by a user of a remote device. A software automation test case is generated using one or more phrases extracted from the digitized voice segment. The software automation test case is executed against a plurality of browser-based software applications using a plurality of automation testing tools, including converting the software automation test case into a plurality of tool-and-browser specific test cases, each based upon test case requirements of a selected automation testing tool and test case requirements of a selected browser-based application. An automation execution report is generated based upon the execution of each of the plurality of tool-and-browser specific test cases.

Abstract: The invention relates to computer technology, and in particular, to a method for achieving remote updating of application programs in a distributed application environment as well as a terminal management system for realizing the method.

Abstract: Apparatus, systems, and methods for a compiler are described. One such compiler converts source code into an automaton comprising states and transitions between the states, wherein the states in the automaton include a special purpose state that corresponds to a special purpose hardware element. The compiler converts the automaton into a netlist, and places and routes the netlist to provide machine code for configuring a target device.

Abstract: Methods, systems, and software for providing or utilizing a software solutions bag of development components and enterprise knowledge—whether developed internally or by third parties—are described herein. One method for managing reusable development components comprises providing a catalog of a plurality of development components to a user. The cataloged development components may include or reference at least a first development component of a first type and a second development component of a second type. A software solutions bag is then generated based on a user selection of at least one of the cataloged development components.