Abstract: A system for safely reverting merges across branches in version control systems where shared history cannot be rewritten is described. A computer-implemented method, comprising: identifying a first merge base at a trunk, the first merge base merging with a branch of the trunk; identifying, at the branch, a second merge base, subsequent to the first merge base, the second merge base merging with the trunk; forming a merge base patch branch from the branch at the second merge base, the merge base patch branch including a copy of the first merge base; merging the merge base patch branch with the trunk; and merging the merge base patch branch with the branch.

Abstract: An information processing apparatus includes a processor that executes a first program. The processor is configured to acquire update information for executing update from the first program to a second program, execute the update by using the update information, accept a request for a function of the first program in a case where at least one of plural information processing apparatuses constituting a cluster has not completed the update, the plural information processing apparatuses being the information processing apparatus and one or more other information processing apparatuses, and provide a function of the second program to a user in a case where all the plural information processing apparatuses have completed the update.

Abstract: Indications of a plurality of events whose occurrence is detected in a particular execution of a program are obtained. One or more partitions of a trace object corresponding to the execution are constructed, including a first partition corresponding to a first subset of the events. The first partition comprises a header portion which includes a compressed representation of one or more event chains, and a data portion comprising a compressed events record indicating an occurrence, during the execution, of a particular sequence of events indicated by an event chain. The trace object is stored.

Abstract: A system for providing an automatic software upgrade assistant for remote elevator monitoring experts using machine learning. The system performs operations that include receiving a request from a requestor to install a software upgrade on a controller of an elevator component, the software upgrade dependent on at least one software program being installed on the controller. It is determined whether the at least one software program is installed on the controller. Based at least in part on determining that the at least one software program is installed on the controller: an elapsed time to complete the installation of the software upgrade on the controller is predicted; and an indication is output to the requestor that the software upgrade is permitted to be installed on the controller and the predicted elapsed time to complete the installation.

Abstract: Techniques are disclosed for generating a dynamic upgrade prediction. The prediction includes generating an initial upgrade prediction for an upgrade to be performed on a subset of component nodes; performing a real time progress review, using a centralized management node, of the upgrade, wherein each of the component nodes includes a number of stages; performing an upgrade duration comparison between the initial upgrade prediction and a real time upgrade time for a subset of the stages; and generating an updated upgrade prediction for the multi-component product upgrade based on the comparison between the initial upgrade prediction and the real time upgrade time.

Abstract: An example operation includes one or more of detecting, by a transport, a difference between sensor data associated with a location outside the transport and data stored on the transport and updating, by the transport, the data stored on the transport with the difference.

Abstract: A device may receive requirement data identifying a requirement for modification of software code, and may process the requirement data, with a machine learning model, to identify entities and intents in the software code and to generate a query. The device may process the query, with a code locator model, to encode text of the query into high-dimensional vectors and to identify a semantic similarity between the high-dimensional vectors and code text. The device may process the query, the semantic similarity, and the code text, with a code developer model, to generate metadata, and may utilize the metadata to identify an identifier associated with the software code. The device may determine, utilizing the identifier, a portion of the software code, and may modify the portion of the software code based on the query to generate modified software code. The device may perform actions based on the modified software code.

Abstract: The technology disclosed relates to systems and methods for deploying cross-platform applications to tiny ML hardware. The system provides tools to maintain definitions of a first, a second and a third declarative instruction. The system provides tools to maintain compiled bytecode for a procedure block and a tiny ML model that runs on the tiny ML hardware. The compiled bytecode further includes a manifest of one or more capabilities, one or more procedure blocks and at least one output supported by the tiny ML model. The system provides a loader that connects to an instance of the tiny ML hardware. The loader includes logic to verify that the instance of the ML hardware supports the one or more capabilities, the one or more procedure blocks and at least one output specified in the manifest. The loader loads the bytecode and verifies integrity of the load.

Abstract: Described herein is a computer implemented method for managing a repository that includes one or more component packages and a repository configuration file listing repository dependencies. Each component package has a package configuration file listing package dependencies. The method including the steps of: parsing the repository configuration file; aliasing a package dependency listed in the repository configuration file with at least two repository dependency aliases; parsing a package configuration file; and linking each repository dependency alias to a package dependency listed in the package configuration file.

Abstract: Software-update risks can be mitigated for end users by implementing some examples described herein. In one example, a system can receive an indication that an end user used a particular feature of an existing version of a software application on a computing device of the end user. The system can also determine that an update for the software application includes a code change to the particular feature. The system can generate a risk score for the update based on the code change. The system can then generate a graphical user interface indicating the risk score for the end user. This may assist the end user in determining whether to apply the update to the existing version of the software application.

Abstract: In a computer-implemented method for using an application platform to design an application, an interface for developing an application is displayed at a computer system, the interface including a plurality of components for use in visually designing the application. A selection of a component is received at the interface. A placement of the component in the application is received within the interface. The application is compiled such that the application executes natively on a target processor, and where the application is bound directly to a native graphics library associated with the target processor. A style selection for the component of the application is received, the style selection modifying an appearance of the component. The application including the style selection is executed within the interface during design time such that the component is rendered according to the style selection without re-compiling the application.

Abstract: A first vehicle includes a wireless transceiver; and a processor programmed to responsive to encountering a second vehicle, establish a wireless connection to the second vehicle via the wireless transceiver and obtain a vehicle identification of the second vehicle, identify a software update for a controller of the second vehicle using the vehicle identification, wherein the software update is incompatible with the vehicle, responsive to connecting to a predefined wireless network, download the software update into a local storage, and responsive to reencountering the second vehicle, reconnect to the second vehicle via the wireless transceiver and transmit the software update to the second vehicle.

Abstract: A system and method for feature switching in software applications. A feature switching action (FSA) is received and at least one user device is identified based on the received FSA. At least one feature switching instruction (FSI) is generated based on the received FSA and the FSI is sent to at least one of the identified user devices. A feature switching instruction response (FSIR) is received from each user device that received a FSI and a feature switching action response (FSAR) is generated based on the received FSIRs.

Abstract: Disclosed herein are system, method, and computer program product embodiments for determining an appropriate FPGA for a particular computer program. An embodiment operates by a central processing unit's counter identifying a plurality of workload properties in processing a computer program, wherein the central processing unit is part of a first computer architecture. The central processing unit then sends the workload properties to a controller trained to identify a field-programmable gate array (FPGA) module based on the plurality of workload properties. The central processing unit thereafter receives a recommended FPGA module from the controller and implements the recommended FPGA module in a computer architecture for processing the computer program, whereby the second computer architecture is able to perform the computer program more efficiently than the first computer architecture.

Abstract: Systems and methods for redeploying source code are disclosed. The method includes receiving a request for previewing redeployment of a selected source code deployment in a target environment. The request includes an identifier of the selected source code deployment and an identifier of the target environment. In addition, the method includes identifying a source code revision identifier of the selected source code deployment, and identifying a source code revision identifier of the latest source code deployment in the target environment. Based on this information, the method retrieves a list of source code revisions between the selected deployment and the latest deployment in the target environment. The retrieving is based on the source code revision identifiers of the selected source code deployment and the latest source code deployment. The method forwards the retrieved list of source code revisions to a client device for rendering on a display of the client device.

Abstract: Mobile devices worldwide execute applications that utilize data services, with issues involving the transfer of data via networks impacting the operation and user experience of those applications. Data is acquired from a mobile computing device executing an application and processed to determine occurrence of a group of related activities performed when executing the application. Parameters of the activities are analyzed, and those parameters associated with poor performance are presented in a user interface. The interface provides impact information about the effect of the activities on operation of the application and may include recommended actions to mitigate the poor performance. A user may interact with data within the interface to trigger a workflow to analyze indicated portions of the data. Subsequent results of this analysis may be returned to the user via the user interface or may be implemented as analytic rules for subsequent data processing.

Abstract: In various embodiments, a method, apparatus, and computer program product are provided involving, at a first device: opening the application on the first device, performing an action utilizing an application, updating a state of the application, for being communicated with the second device; and, at a second device: utilizing the updated state of the application received from the first device, displaying an interface including: a button for opening the application utilizing the second device, and indicia that indicates that the first device has updated at least one aspect of the application, and in response to a detection of the selection of the button, accessing the application utilizing the second device such that the application is accessed so as to reflect the updated state of the application.

Abstract: Techniques for monitoring operating statuses of an application and its dependencies are provided. A monitoring application may collect and report the operating status of the monitored application and each dependency. Through use of existing monitoring interfaces, the monitoring application can collect operating status without requiring modification of the underlying monitored application or dependencies. The monitoring application may determine a problem service that is a root cause of an unhealthy state of the monitored application. Dependency analyzer and discovery crawler techniques may automatically configure and update the monitoring application. Machine learning techniques may be used to determine patterns of performance based on system state information associated with performance events and provide health reports relative to a baseline status of the monitored application. Also provided are techniques for testing a response of the monitored application through modifications to API calls.

Abstract: Aspects of the disclosure relate to conducting software testing using dynamically masked data. In some embodiments, a computing platform may receive, from a developer computing platform, a test execution request that includes a test code for execution. Subsequently, the computing platform may establish a secure connection to an enterprise data storage database. Upon establishing the secure connection, the computing platform may request confidential data from the enterprise data storage database in connection the test execution request. Thereafter, the computing platform mat execute the test code, which may include receiving encrypted confidential data from the enterprise data storage, decrypting the confidential data, and plugging the confidential data into the test code.

Abstract: A device may log update information associated with an operation, wherein the update information identifies one or more changes made to the dataset during the operation and a source of the operation. The device may identify, based on identification information associated with the dataset, a lineage record identifier associated with the dataset. The device may generate a lineage record associated with the operation, wherein the lineage record includes the lineage record identifier and the update information. The device may send a request for validation to an authorized node to validate the lineage record, wherein the authorized node is authorized to access the dataset. The device may store, based on the lineage record being validated by the authorized node, the lineage record in a distributed ledger, wherein the distributed ledger is accessible to a plurality of nodes to enable the plurality of nodes to access the update information.