Abstract: Systems and methods are described for comparing execution of two or more artificial intelligence (AI) AI agents. A platform can provide a user interface (UI) that allows for selection or creation of multiple AI agents. The AI agents can utilize different agent objects, such as different prompts, datasets, or models. The AI agents can be displayed on a single UI screen, where execution of the AI agents is simultaneously simulated. The same inputs can be provided to the multiple AI agents, and the corresponding outputs can display on screen. The platform can also vectorize and compare the semantic similarity of the outputs, presenting an indication of the semantic similarity on the same UI screen.

Abstract: A method performed by a relay server for facilitating communications between a web application executing in a web browser and one or more client computing devices. The method includes receiving a selected domain name under which the web application is to be registered, verifying that the web application is allowed to be registered under the selected domain name based on accessing a record associated with the selected domain name in a domain name system (DNS) database, registering the web application under the selected domain name, relaying messages associated with the selected domain name that are received from the one or more client computing devices to the web application over a first bidirectional communication connection established between the web application and the relay server, and relaying messages received from the web application over the first bidirectional communication connection to respective ones of the one or more client computing devices.

Abstract: Methods, system, and non-transitory processor-readable storage medium for a regression detection testing system are provided herein. An example method includes receiving a pull request to merge software code changes and parsing a pull request code difference file to identify a plurality of software modules and software functions. A test case attribute associated with a test case is queried to identify a software module associated with the test case. If the plurality of software modules and software functions comprises the software module, the test case is added to a first plurality of test cases. If the plurality of software modules and software functions comprises at least one software function, and the test case comprises that software function, the test case is added to a second plurality of test cases. At least one of the first and the second plurality of test cases are executed on a test system.

Abstract: Aspects of the present disclosure relate generally to software development environments and, more particularly, to predicting runtime errors in software development environments. For example, a computer-implemented method includes: clustering similar regions of source code into clusters of code regions; identifying source code exceptions from at least one past execution of an executable image of the source code; deriving a model of features of the source code associated with the source code exceptions for the clusters of code regions; generating a matrix as output of the model that predicts a likelihood of an occurrence of at least one uncaught exception during a future execution of the executable image of the source code in a cluster of the clusters of code regions; and annotating the source code in the code region of the cluster with an indication of the likelihood of the occurrence of the at least one uncaught exception.

Abstract: A technique is directed to ascertaining application test coverage. The technique involves receiving a command to test an application having a set of unmarked sections and a set of marked sections. The command includes a selection parameter that requests at least one of unmarked section coverage results and marked section coverage results. The technique further involves running a test procedure that operates the application to generate section coverage data. The technique further involves, after running the test procedure, generating application coverage results from the section coverage data. The application coverage results describes test procedure coverage of at least one of the set of unmarked sections of the application and the set of marked sections of the application based on the selection parameter of the command.

Abstract: Systems and methods for simulated reality view-based breakpoints are described. Some implementations may include accessing motion data captured using one or more motion sensors; determining, based at least on the motion data, a view within a simulated reality environment presented using a head-mounted display; detecting that the view is a member of a set of views associated with a breakpoint; based at least on the view being a member of the set of views, triggering the breakpoint; responsive to the breakpoint being triggered, performing a debug action associated with the breakpoint; and, while performing the debug action, continuing to execute a simulation process of the simulated reality environment to enable a state of at least one virtual object in the simulated reality environment to continue to evolve and be viewed with the head-mounted display.

Abstract: A method is provided for identifying a data transfer mismatch between a sender and a receiver from among units of a software simulator of a hardware processor. The simulator runs the plurality of the units which communicate with each other via First-In First-Outs (FIFOs). The method counts amounts of data the sender writes to the FIFOs and the receiver reads from the FIFOs for a given data transfer. The method avoids blocking during FIFO reading and writing operations by (i) reading dummy data by the receiver, even if the FIFOs are empty, when the receiver tries reading from the FIFOs, and (ii) discarding written data if the FIFOs are full, when the sender tries writing to the FIFOs. The method identifies mismatches in the amount of data the sender writes to the FIFOs versus the amount of data the receiver reads from the FIFOs for the given data transfer.

Abstract: Systems and methods for generating and testing on-chain programs are disclosed herein. A system for generating on-chain programs may receive a request to generate on-chain program code for an on-chain program and determine a model required for the program. The system may retrieve functions associated with the model and determine blockchain operations to be added to the program. The system may determine parameters for blockchain operations and generate on-chain program code. A system for testing on-chain programs may install an on-chain program onto a test blockchain and retrieve functions associated with a model generated for testing. The system may generate blockchain operations for testing and input each operation into a cryptography-based storage application. The system may cause execution of the operations and receive results. Based on determining that a number of failed results exceed a threshold, the system may generate a notification.

Abstract: Methods, systems, and computer-readable media for analysis of code coverage differences across environments are disclosed. A code coverage profiling system determines a first code coverage profile associated with execution of program code in a first environment. The first code coverage profile indicates one or more portions of the program code that were executed in the first environment. The code coverage profiling system determines a second code coverage profile associated with execution of the program code in a second environment. The second code coverage profile indicates one or more portions of the program code that were executed in the second environment. The code coverage profiling system performs a comparison of the first code coverage profile and the second code coverage profile. The comparison determines a difference between the portions of the program code that were executed in the first and second environments.

Abstract: Metadata objects describing a resource may be generated by multiple processes in the IT system and be of different metadata formats. These metadata objects may be parsed into a unified semantic graph over which validation rules may be applied. The semantic graph and a validation ruleset comprising one or more validation rules may be input into a validation engine. The validation engine may interpret the validation into logical assertions then apply them over the semantic graph. The validation engine may then generate a validation report indicating whether the graph is conformant. The validation report may include information about any validation failures that may have occurred and may be displayed to a user on a client device via a graphical user interface.

Abstract: The present disclosure relates to a field of computer technologies, and discloses a method, an apparatus, a computer device, and a storage medium for determining page jump information. The method includes: monitoring a page state of a page routing stack; in response to the page state changing, determining a current page and a previous page; detecting whether a page type of the current page is the same as a page type of the previous page; in response to the page type of the current page being different from the page type of the previous page, determining a first page type corresponding to the current page and a second page type corresponding to the previous page; determining page tracking information for the current page based on the first page type and the second page type; and determining page jump information corresponding to the current page based on the page tracking information.

Abstract: Methods, systems, and apparatus, including computer programs encoded on computer storage media, for generating a set of target language code from a set of source language code. One of the methods includes obtaining input data that represents a set of source language code; and processing the input data to generate a set of target language code.

Abstract: A programming assisting program causes a computer to function as a calculator that acquires, from a database storing information indicating an address space in a memory having a range pre-allocated to each type of component included in a project performed by a PLC, the information indicating the address space, and allocates components to the address space to calculate a use volume in the memory used by the project for each type of component, a determiner that determines, based on the use volume and an allocated volume in the memory determined based on the pre-allocated range, an allocated volume allocated to each type of component, a changer that changes, based on the determined allocated volume for each type of component, the range pre-allocated to each type of component, and a display that displays, for each type of component, the calculated use volume and the determined allocated volume on a screen.

Abstract: Services provided by a platform may be described in a uniform way via service-specific provisioning descriptors. To provision services for a client system, a managed services provisioning system provides a service configuration interface through which a service associated with a tuple of a particular sender, receiver, and document type can be selected for further configuration. A service provisioning interface is dynamically generated for obtaining service-specific provisioning information from a user for generating a service-specific provisioning data instance that can be deployed to a backend system. At runtime, the backend system utilizes the service-specific provisioning data instance to provide the provisioned service for a client system. In this way, a variety of services can be efficiently provisioned for a diverse set of clients.

Abstract: A system for automatically tracking elements associated with a software application and for generating customizable graphs that capture the dependencies and message flows among the elements is provided. For a software application deployed in a cloud environment, configuration files used to deploy the elements of the software application are processed to extract information such as the name of each element and the names of messages used or produced by each element. This extracted data is combined with implicit data about the cloud environment such as data about elements used in the environment but that are not deployed using configuration files. Graph data is generated from the combined data that includes an object for each element and edges that represent message flows or dependencies between the elements. The graph data is used to render and display a graph of the software application.

Abstract: Systems and methods are described for comparing execution of two or more artificial intelligence (AI) pipelines. A platform can provide a user interface (UI) that allows for selection or creation of multiple AI pipelines. The AI pipelines can utilize different pipeline objects, such as different prompts, datasets, or models. The AI pipelines can be displayed on a single UI screen, where execution of the AI pipelines is simultaneously simulated. The same inputs can be provided to the multiple AI pipelines, and the corresponding outputs can display on screen. The platform can also vectorize and compare the semantic similarity of the outputs, presenting an indicating of the semantic similarity on the same UI screen.

Abstract: Idiomatic generation of language-specific bindings of application programming interfaces (APIs) is disclosed. A machine learning model may be trained using example programming code and interfaces of a particular programming language to identify design patterns and best coding practices for that language. A specification defining an API may then be provided in a language-neutral format. The specification may then be processed according to the trained model in coordination with language-specific and language-neutral rules to generate an idiomatic interface specification targeting the programming language that incorporates at least a portion of the identified design patterns and best coding practices, where the input specification does not incorporate the identified design patterns and best coding practices.

Abstract: In some examples, a server determines that project code calls a component in a third-party library that has been updated. The server determines a first type hierarchy associated with the component, a second type hierarchy associated with the updated component, and performs a type hierarchy comparison of the first and the second type hierarchy. The server determines a first call graph associated with the component, determines a second call graph associated with the updated component, and performs a call graph comparison of the first and second call graph. Based at least in part on the type hierarchy comparison and the call graph comparison, the server determines a set of breaking changes associated with the updated component, with each breaking change in the set identifying changes to the updated component, relative to the component, that are determined to cause an incompatibility when the project code calls the updated component.

Abstract: An embodiment may involve obtaining a log regarding execution of a software application; obtaining indications of availabilities of resources related to the software application; determining, from the log and the indications of availabilities of the resources, a time series of software application activities; and training a prediction engine with the time series of software application activities, wherein the prediction engine as trained is configured to receive an input time series of further software application activities and generate an output time series that predicts additional software application activities.

Abstract: Systems and methods are provided for analyzing a commit comprising an updated version of software code against a previous version of software code to determine a plurality of methods in the commit that have been changed, identifying a previous version and an updated version for each method that has been changed, and generating graphical representations of each previous version and each updated version of each method that has been changed. The systems and methods further provide for extracting path contexts from each graphical representation for each previous version and each updated version of each method, determining path contexts that are different by comparing each path context for each previous version with an associated updated version of each method, and encoding each path context that is different to generate at least one commit vector representation of the commit.