Abstract: Computer systems, devices, and associated methods of verifying reliability of instructions for a device are disclosed herein. In one embodiment, a method includes identifying a reliability requirement associated with instructions for a device and receiving, from a user, an assertion in relation to the reliability requirement. The method includes generating a cryptographic assertion tracer (CAT) based at least in part on the received assertion. The method includes receiving assertion-related instructions in association with the CAT and generating a first code verification encrypted reproducible record based at least in part on the CAT and the received assertion-related instructions. The method then includes reporting that the reliability requirement is addressed.

Abstract: The sizes of image files for deploying software in a computing environment can be reduced according to some examples described herein. In one example, a system can identify base image files that each include at least a predefined amount of dependencies relied upon by target software. The system can then select a particular base image file, from the base image files, having a smallest size as compared to a remainder of the base image files. The system can then build a customized image file from the base image file, where the customized image file is configured for deploying the target software to a computing environment.

Abstract: A method, apparatus, and a non-transitory computer-readable storage medium for generating heterogenous platform code. The method may obtain a neural network model. The neural network model may be programed to run on at least one platform. The method may also obtain an initial intermediate representation (IR) code by encoding the neural network model, and obtain a target IR code by adding decorations to the initial IR code based on a target platform. The method may also output an executable code optimized to run on the target platform by decoding the target IR code.

Abstract: The present application provides a mobile terminal, a method for uninstalling a pre-installed application therein, and a memory. The method comprises the following steps: obtaining an authorization file for uninstalling a pre-installed application; determining whether the authorization file is valid; if so, determining whether the pre-installed application is a user-level application; and if so, uninstalling the pre-installed application.

Abstract: Systems, methods, and computer programming products for dynamically managing the uninstallation and/or re-installation of software applications stored or accessed by a computing system, including mobile devices. Management of the applications by the system can be periodically managed automatically or based on recommendations. Management of applications being uninstalled or reinstalled may be determined based on a rate a user accesses the application and/or data published or accessible by an application storefront, such as user reviews, storefront rankings, user feedback and uninstallation rates of the applications by other users. Applications experiencing a decreased level of average user satisfaction below a predetermined threshold can be proposed for deletion or automatically deleted. Replacement of underperforming or unsatisfactory applications with alternative applications having similar functionality but a higher rate of user satisfaction can be recommended or installed.

Abstract: A data transmission method includes: obtaining information required for performing an acceleration operation in a virtual input/output ring of a target virtual accelerator, where the information required for performing the acceleration operation uses a predefined data structure, and the data structure occupies one entry of the virtual input/output ring of the target virtual accelerator; determining, according to the information required for performing the acceleration operation, information that can be recognized by the hardware accelerator; and sending the information that can be recognized by the hardware accelerator to the hardware accelerator, where the hardware accelerator is configured to obtain to-be-accelerated data according to the information that can be recognized by the hardware accelerator and perform the acceleration operation on the to-be-accelerated data.

Abstract: A system comprises data processing hardware and memory hardware. The memory hardware is in communication with the data processing hardware, and stores instructions that, when executed on the data processing hardware, cause the data processing hardware to perform a plurality of operations. In some examples, one of the operations may include receiving instance management configuration data for a single-tenant software-as-a-service (SaaS) application. Another operation may include further include receiving an image of the single-tenant SaaS application. Yet another operation can include generating, by the control plane manager, a control plane based on the instance management configuration data. The control plane is configured to create multiple instances of the single-tenant SaaS application based on the received image, and to manage the instances of the single-tenant SaaS application based on the received instance management configuration data.

Abstract: A method for software patching, the method may include determining to expose at least one patch of a version of an operating system to one or more computers located outside a unified local path repository (ULPR) hosted by a computer; and exposing, for period of time and by the ULPR, a selected logical computer that stores the at least one patch. The selected logical computer is selected out of multiple logical computers of the ULPR. Different logical computers of the multiple logical computers store operating systems that differ from each other by at least one of identity and version.

Abstract: Software systems and methods convert algorithms and software codes into time affecting linear pathways (TALPs) via decomposition and convert paired Input/Output (I/O) datasets into TALPs via Value Complexity polynomials. Generated TALPs can be enhanced through merging with other TALPs. TALPs can be grouped by matching the outputs of the TALP-associated prediction polynomials with some set of given criteria into families and cross-families that are useful in a new type of software optimization that allows for output values of grouped TALPs to be modeled, pooled, discretized and optimized to enhance goals or meet user goals.

Abstract: The present disclosure relates to systems and methods for code optimization. The methods include generating, based on a first macro of a user code, an assembly code corresponding to the user code. The first macro includes one or more parameters relating to one or more branch codes, and the assembly code includes assembly branch codes corresponding to the branch codes and jump codes corresponding to the assembly branch codes. The methods further include obtaining, based on a second macro of the user code, target information for identifying an execution condition of the one or more branch codes, and determining, based on the assembly code and the target information, a compiled user code. When being executed, the compiled user code may call, based on the target information, a procedure to determine a value of the execution condition. The procedure is configured to modify an execution flow of the compiled user code.

Abstract: The disclosure provides for analyzing upgrade and migration readiness. Embodiments include receiving an indication to upgrade a software product and a selected upgrade path identifying a target-upgrade version. Embodiments include accessing an array of pre-upgrade procedures comprising code for identifying one or more conditions that must be met before the software product can be upgraded based on the accessed array being associated with the software product. Embodiments include executing one or more of the pre-upgrade procedures in advance of upgrading the software product. Embodiments include accessing one or more autonomous remediation scripts from the repository based on identification of one or more failed pre-upgrade procedures. Embodiments include executing the one or more autonomous remediation scripts to cure the one or more failed pre-upgrade procedures and initiating an upgrade of the software product based on identifying that the array of pre-upgrade procedures successfully completed execution.

Abstract: Software code is tested to determine relative performance of the software code. Successfully executing a test may be used to flag problems in a code repository to be corrected or criteria for accepting code for acceptance to the repository. To further evaluate test results, the test may be run several times on the same code version to determine a test result stability score describing how the test results may vary in different executions, such as a frequency that the code passes the test. Based on the score, additional tests may be run to further refine test result stability score. To evaluate time-variance of testing, when a code version fails a test, a previous version of the code may be run with the same test and the results compared to determine if a new regression was introduced.

Abstract: Aspects of the present disclosure relate to personalized software release note generation. Software usage of a user with respect to a software application can be tracked. Software release notes of the software application can be analyzed with respect to the software usage. Personalized software release notes can be generated for the user based on the analyzing. The personalized software release notes can be presented to the user.

Abstract: A software operator can be automatically configured and deployed in a distributed computing environment from a package. For example, a system can receive a command specifying a package for deploying a target operator. In response to receiving the command, the system can automatically configure and deploy the target operator in a computing cluster. This may involve the system extracting a name for the target operator from the corresponding package and assigning an operator group to the target operator. The system can then subscribe the target operator to an operator management system by indicating the name and a namespace of the operator group to one or more application programming interfaces of the computing cluster. The system can also deploy an instance of the target operator in the namespace on the computing cluster.

Abstract: A system and method for identifying and removing dead-code from a computer program of an independent service is provided. The method includes: retrieving information related to the code of the service, wherein the retrieved information includes at least static and dynamic dependencies information of classes of the service; constructing a static dependencies graph, wherein nodes of the static dependencies graph are classes, and directed edges depict static dependencies between classes; classifying classes based on the static dependencies; constructing a first subgraph to include classes classified as internal-pure-static (IPS) classes; detecting external-dead-class candidates by traversing the subgraph; adding external-dead-class candidates to a dead code cut (DCC) set; and removing at least one class included in the DCC set from the code of the service.

Abstract: Systems and methods for data storage device firmware updates in a composable infrastructure are described. Recomposition of a system in a composable infrastructure may include downloading a firmware update to a data storage device, activating the firmware update in the data storage device, and receiving a reset command at the data storage device. The reset command may include a step to flush a virtual-to-physical (V2P) mapping table from a volatile memory in the data storage device to non-volatile memory devices in the data storage device. Responsive to a flag that is set and the received reset command, the data storage device may forgo the step of flushing the V2P mapping table.

Abstract: A system includes a memory programmed with multiple firmware images each having a distinct entry point, a processor, a writable hardware register initially seeded with an initial firmware image entry point address. A controller external to the processor, prior to an initial processor reset, reads the hardware register and causes the processor to begin fetching instructions at the initial firmware image entry point read from the hardware register. Prior to a subsequent reset, the external controller facilitates at least one transition to at least one of the multiple firmware images other than the initial firmware image by reading the entry point of the other firmware images from the hardware register and causing the processor to begin fetching instructions at the entry point of the other firmware images read from the hardware register.

Abstract: A system and method for prepopulating a container image repository for continuous integration (CI/CD) environments using volumes and/or layered images. The method includes executing, by the processing device, a container image that is configured as an image repository mirror for a remote server. The method includes executing, by the processing device, an application to cause the application to provide a request for one or more images to the container image. The method includes determining, by the container image, an absence of the one or more images in the container image. The method includes retrieving, by the container image responsive to determining the absence of the one or more images, the one or more images from the remote storage. The method includes providing, by the container image, the one or more images retrieved from the remote storage to the application.

Abstract: Embodiments of the disclosure provide systems and methods for managing a lifecycle of a software application. According to one embodiment, software application lifecycle management can comprise receiving a specification for an application. The specification can comprise an executable script defining a plurality of features for the application and a plurality of scenarios. Each scenario representing a test for one or more features of the application and each feature comprising one or more user stories. A test entity can be created for and corresponding to each scenario in the specification and each scenario can be marked with a test identifier linking the created test entity to the corresponding scenario in the script. Results of execution of one or more scenarios of the plurality of scenarios can be received and reported on a per-feature and per-scenario basis.

Abstract: Techniques are disclosed for deploying functions in a cloud computing environment. Parameters are annotated in a plurality of Helm charts with a predetermined token. Duplicated values in the Helm charts are identified and the predetermined token is reused for the duplicated values. Schema files from the plurality of Helm charts are parsed to extract the predetermined tokens. Input data are received as values for the predetermined tokens. The function is deployed in the cloud computing environment using the values for the predetermined tokens as parameters in the Helm charts.