Abstract: Techniques for recording submissions of a user actions in relation to interface elements of a GUI for replay are disclosed. Data arguments generated in response to the user actions required for executing a command associated with the user actions are recorded. A system monitors execution of an application. The system detects a command or action that corresponds to submission of a user action in relation to target interface elements displayed by a GUI. When the system detects the command, the system records the user action in relation to the target interface element and data arguments selected for executing the command. When the system receives a request to replay the submission of the user action, the system retrieves the data arguments for executing the command and causes execution of the command by submitting the user action to the GUI along with the data arguments for executing the command.

Abstract: A method may include obtaining machine-readable source code. The method may include parsing the source code for one or more code descriptions and identifying a section of the source code corresponding to each of the code descriptions. The method may include determining a description-code pair including a first element representing the code description and a second element representing the section of the source code corresponding to the code description. The method may include generating an augmented programming language corpus based on the description-code pair, the one or more code descriptions, and the source code. The method may include receiving a natural language search query for source-code recommendations, identifying source code from the augmented programming language corpus responsive to the natural language search query, and responding to the natural language search query with the identified source code.

Abstract: A method may include obtaining machine-readable source code. The method may include parsing the source code for one or more code descriptions and identifying a section of the source code corresponding to each of the code descriptions. The method may include determining a description-code pair including a first element representing the code description and a second element representing the section of the source code corresponding to the code description. The method may include generating an augmented programming language corpus based on the description-code pair, the one or more code descriptions, and the source code. The method may include receiving a natural language search query for source-code recommendations, identifying source code from the augmented programming language corpus responsive to the natural language search query, and responding to the natural language search query with the identified source code.

Abstract: A device may receive a first sample. The device may identify a plurality of second samples that are similar to the first sample. The plurality of second samples may correspond to service tickets that have previously been processed. The device may obtain or determine log information identifying a plurality of events associated with the first sample. The device may determine respective probabilities of occurrence corresponding to the plurality of second samples. A probability of occurrence, for a particular second sample, may identify a likelihood of receiving a corresponding service ticket within a particular time period of occurrence of the plurality of events. The device may assign ranks to the plurality of second samples based on the respective probabilities of occurrence. The device may provide information identifying the ranks and the plurality of second samples.

Abstract: In some examples, incident prediction and prevention may include ascertaining a plurality of past incidents, clustering the plurality of past incidents to generate a plurality of incidents clusters, and identifying, for each past incident of the plurality of past incidents that is in a respective incidents cluster of the plurality of incidents clusters, a time of occurrence. Incident prediction and prevention may include ascertaining a new incident, assigning the new incident to an incidents cluster of the plurality of incidents clusters, and determining, for the assigned incidents cluster, at least one further predicted incident associated with at least one further corresponding incidents cluster. Further, incident prediction and prevention may include determining a resolution to the at least one further predicted incident, and preventing occurrence of the at least one further predicted incident by executing the determined resolution to the at least one further predicted incident.

Abstract: A rapid application developer system is disclosed that provides a development platform configured to generate an application manifest document for developing a new target application within a certain industry. The application manifest is generated based on components identified from previously developed applications within the same industry as the target application.

Abstract: In some examples, incident prediction and prevention may include ascertaining a plurality of past incidents, clustering the plurality of past incidents to generate a plurality of incidents clusters, and identifying, for each past incident of the plurality of past incidents that is in a respective incidents cluster of the plurality of incidents clusters, a time of occurrence. Incident prediction and prevention may include ascertaining a new incident, assigning the new incident to an incidents cluster of the plurality of incidents clusters, and determining, for the assigned incidents cluster, at least one further predicted incident associated with at least one further corresponding incidents cluster. Further, incident prediction and prevention may include determining a resolution to the at least one further predicted incident, and preventing occurrence of the at least one further predicted incident by executing the determined resolution to the at least one further predicted incident.

Abstract: A device may receive a first sample. The device may identify a plurality of second samples that are similar to the first sample. The plurality of second samples may correspond to service tickets that have previously been processed. The device may obtain or determine log information identifying a plurality of events associated with the first sample. The device may determine respective probabilities of occurrence corresponding to the plurality of second samples. A probability of occurrence, for a particular second sample, may identify a likelihood of receiving a corresponding service ticket within a particular time period of occurrence of the plurality of events. The device may assign ranks to the plurality of second samples based on the respective probabilities of occurrence. The device may provide information identifying the ranks and the plurality of second samples.

Abstract: A rapid application developer system is disclosed that provides a development platform configured to generate an application manifest document for developing a new target application within a certain industry. The application manifest is generated based on components identified from previously developed applications within the same industry as the target application.