Disclosed are some implementations of systems, apparatus, methods and computer program products for facilitating version control for a client device. A server system may select one of two or more versions of a procedure based, at least in part, on a user profile. The server system may generate a message including a procedure name of the procedure, a version identifier identifying the selected version of the procedure, a set of computer-readable instructions corresponding to the selected version of the procedure, and a client directive pertaining to storing the procedure in a database. The server system may transmit the message to a client device associated with the user.

A method includes receiving a request to process a set of data using a data processing application. The method includes, based on a feature associated with the set of data, selecting between (i) a first mode in which one or more running processes of the data processing application are used to process the set of data and (2) a second mode in which one or more new processes of the data processing application are started up. The method includes causing the data processing application to be executed according to the selected mode to process the set of data.

A method, computer system, and computer program product for migrating a service (e.g. microservice) from using a first application programming interface version to using a second (e.g. newer or updated) application programming interface version. The method may include determining a difference between specifications of the first and second versions of the application programming interface. Historical usage of the first version of the application programming interface by the service may then be analyzed with respect to the difference so as to determine if the service meets the specification of the second version of the application programming interface. Responsive to determining the service meets the specification of the second version of the application programming interface difference, the service may be migrated from using the first version of the application programming interface to using the second version of the application programming interface.

Embodiments of a system, methods, and other techniques and configurations for automation of computing system maintenance activities such as reboots, software installations, re-configuration, or other actions are generally described herein. In an example, an automation tool set is designed to integrate with an organization Configuration Management Database (CMDB) and other orchestration or information technology (IT) management tools to perform such maintenance actions. The automation tool set may enable and manage various forms of a workflow for maintenance actions, including a workflow designed to validate all necessary pre- and post-reboot checks, perform logging, event tracking, exception handling, notifications, incidents creation, trend analysis, customized reporting dashboards, and system adaptation. In further examples, the automation tool set may expose user interfaces, reports, and other management interfaces for control and monitoring of the workflows.

A method and system for deploying an application from a deployment source to a device may include determining if the application is available for deployment to the device from a plurality of deployment sources, upon determining that the application is available for deployment from the plurality of deployment sources, identifying one of the plurality of deployment sources as a preferred deployment source for deploying the application; and deploying the application from the preferred deployment source to the device. Deploying the application may include installing the application, loading one or more user interface elements associated with the application and activating the application.

A system for performing code security scan includes a non-transitory computer readable medium and a processor. The non-transitory computer readable medium stores a plurality of identifiers each identifying a software security analysis tool of one of several categories, including SAST, DAST and OSA tools. The processor receives an identification of code to be scanned. The processor selects at least two identifiers from the plurality of identifiers. The at least two identifiers identify at least two select software security analysis tools for execution on the identified code. The processor receives an execution result from each select software security analysis tool after performing execution on the identified code. The processor aggregates the execution result from each select software security analysis tool. A user interface displays an aggregation of the execution result from each select software security analysis tool.

A parametric constant resolves to different values in different contexts, but a single value within a particular context. An anchor constant is a parametric constant that allows for a degree of parametricity for an API point. The context for the anchor constant is provided by a caller to the API point. The anchor constant resolves to an anchor value that records specialization decisions for the API point within the provided context. Specialization decisions may include type restrictions, memory layout, and/or memory size. The anchor value together with an unspecialized type of the API point result in a specialized type of the API point. A class object representing the specialized type is created. The class object may be accessible to the caller, but the full value of the anchor value is not accessible to the caller. The API point is executed based on the specialization decisions embodied in the anchor value.

Among other things, techniques for securely booting processors in a vehicle are described. An apparatus comprises a circuit coupled to one or more processors of a vehicle and managing a secure boot process for the processors. The circuit receives an indication that the vehicle has been powered on and sends, to a network server, a request for boot files for the processors of the vehicle. In response, the circuit receives, from the server, most recent versions of boot files respectively corresponding to the processors, wherein each boot file includes a digital signature of a trusted authority. In response to obtaining the most recent versions of the boot files, the circuit sequentially boots the processors using the respective boot files, wherein each processor executes a corresponding boot file upon verifying authenticity of the digital signature in the boot file using a corresponding class authentication key.

Provided is a multi-language scheduling method. The method is applied to an embedded device. The method includes: receiving a language scheduling request from a terminal, where the language scheduling request includes a language pack identifier; when it is determined that there is not a language pack corresponding to the language pack identifier in a memory of the device, loading the language pack corresponding to the language pack identifier from an external storage medium of the device into the memory of the device; and then, obtaining the language pack corresponding to the language pack identifier from the memory of the device and returning the language pack to the terminal.

A port descriptor version of a port descriptor to be obtained is selected. An indication of the port descriptor version is provided in a command to be preceded before another command used to obtain the port descriptor. The other command uses the port descriptor version to obtain the port descriptor. The port descriptor is obtained, and the port descriptor includes information relating to a port to be used in communication within the computing environment.