Abstract: Systems and methods associated with performing checkpoint and build processing associated with a continuous integration/continuous deployment (CI/CD) pipeline. In one embodiment, an exemplary method may include identifying an outside dependence for a new cloud process to be integrated into a CI/CD build of a CI/CD pipeline, determining on a periodic or ongoing basis whether a current status of the outside dependence identifies it as incomplete such that a new cloud process would not perform as desired until the dependence is complete, preventing the new cloud process from being integrated into the CI/CD build until the current status indicates that the outside dependence is complete, and integrating the new cloud process into the CI/CD build when the current status indicates that the outside dependence is complete.

Abstract: A tracing controller may utilize a binary execution trace mechanism to trace execution of compiled application machine code. The tracing controller may initiate hardware tracing to gather control-flow hardware traces of a method executing on a processor configured to generate hardware tracing information. The controller may generate a profile based on the hardware tracing information and initiate re-compiling or re-optimizing of the method in response to determining that the new profile differs from the previous profile. The controller may repeatedly profile and re-optimize a method until profiles for the method stabilize. Profiling and hardware tracing of an application may be selectively enabled or disabled allowing the controller to respond to later phase changes in application execution by re-optimizing, thereby potentially improving overall application performance.

Abstract: Techniques for subject matter expert identification for computer software are described herein. An aspect includes receiving a search string. Another aspect includes searching a plurality of library usage data files to determine a selected library corresponding to the search string. Another aspect includes determining a location of a library call corresponding to the selected library in source code. Another aspect includes determining a computer programmer associated with the determined location based on version control metadata corresponding to the source code. Another aspect includes identifying the determined computer programmer as a subject matter expert for the selected library.

Abstract: Techniques for build recovery from inter-code commit failure. A build error for a software project is identified. A first software module, with one or more errors related to the build error, is selected. A comparison software module for the first software module is identified. The comparison software module includes at least one of: (i) a sibling software module to the first software module or (ii) an earlier version of the first software module. A potential problem with the first software module, related to the build error, is determined based on comparing the first software module with the comparison software module. A solution to the potential problem is generated based on the first software module. The solution includes a modification to the software code of the first software module. The solution is applied by modifying the software code of the first software module.

Abstract: The present specification provides a method for executing a smart contract, a blockchain node, and a storage medium. An implementation of a method for executing a smart contract includes: receiving, by a blockchain node, a request for creating a smart contract, the request including a bytecode of the smart contract; starting, by the blockchain node after completing deployment of the smart contract, to compile the bytecode of the smart contract into a machine code by using ahead of time (AoT) compilation and storing the machine code; and during execution of a smart contract that has been deployed, interpreting and executing, by the blockchain node, a bytecode of the smart contract in response to that a machine code of the smart contract is not locally stored.

Abstract: Systems and methods for aggregating a dependency structure based on application logging data, application metadata, customer intent and journey, organizational structure, and operational support information. The method includes receiving data using an application programming interface. The method further includes, for each user, determining a start point and an end point corresponding to user activity on a networked system. The method also includes, for each user, determining a task based on the start point and end point corresponding to the user activity. The method further includes, for each user, determining operations data corresponding to the user activity. The method also includes, for each user, determining a dependency structure based on the task and the operations data. The method also includes aggregating the dependency structure, the task, and the operations data into a visualization. The method further includes generating for display the visualization on a user device.

Abstract: A system and a method of updating a computing device of an information handling system (IHS), including identifying a reboot of the IHS; determining whether the reboot of the IHS is classified as a normal reboot of the IHS or is classified as a failure-reboot of the IHS; when it is determined that the reboot of IHS is classified as a failure-reboot of the IHS: obtaining an activation time period of a scheduled update to the computing device; obtaining a current date and time of the IHS; determining whether the current date and time of the IHS is within the activation time period of the scheduled update to the computing device; and when it is determined that the current date and time is within the activation time period of the scheduled update, transferring update firmware to the computing device for activation at the computing device.

Abstract: Techniques for an ultra-fast installation of a new operating system are provided. Conventional dependencies are ignored in a way that allows multiple components to be installed at once, even when certain components traditionally could not be installed until one or more other components had successfully completed their installation. An operating system executing on a computing device receives a container with files that collectively include a new operating system and a definition with the locations for the files in memory. An uninstalled state may be assigned to each file. Each file may be moved from the container to the location specified in the definition in parallel and independently of other files. After each file is moved, each file may be switched from the uninstalled state to the installed state. The new operating system may be transitioned from an uninstalled state to an installed state once files are switched to installed states.

Abstract: An industrial integrated development environment (IDE) supports collaborative tools that allow multiple designers and programmers to remotely submit design input to the same automation system project in parallel while maintaining project consistency. These collaborative features can include, for example, brokering between different sets of design input directed to the same portion of the system project, generating notifications to remote designers when a portion of the system project is modified, sharing of development interfaces or environments, facilitating involvement of outside technical support experts to assist with design issues, and other collaborative features.

Abstract: A first instance of a managed runtime environment is provided. An optimized version of a code unit and a corresponding set of one or more speculative assumptions are received at the first instance of the managed runtime environment, wherein the optimized version of the code unit produces the same logical results as the code unit unless at least one of the set of one or more speculative assumptions is not true, and wherein the optimized version of the code unit and the corresponding set of one or more speculative assumptions are generated by an entity that is different from the first instance of the managed runtime environment. The optimized version of the code unit is executed at the first instance of the managed runtime environment. Whether the set of one or more speculative assumptions hold true is monitored at the first instance of the managed runtime environment.

Abstract: An object of the present disclosure is to determine whether or not communication between ECUs after update of a software program is expected communication. A vehicular communication system includes: a storage unit which stores a first piece of information indicating data scheduled to be transmitted and received on a bus connecting a plurality of ECUs so that the ECUs can communicate with one another; an acquiring unit which acquires a second piece of information indicating data being transmitted and received on the bus when a software program of at least one of the plurality of ECUs is updated; and a determining unit which determines whether or not expected communication is being executed on the bus based on the first piece of information and the second piece of information.

Abstract: Software for a computer system may be automatically generated to reduce costs. Software may be automatically generated using a set of software components where each component may have one or more input properties and one or more output properties. A property may correspond to a type of data (e.g., a customer ID) used by the computer system. A graph may be created from the components where the graph includes component nodes for the components and property nodes for the input and output properties. To automatically generate software for a task, a task specification may be received that includes a task input property and a task output property. A path on the graph may be determined from the task input property and the task output property, and software for accomplishing the task may be generated using components on the path. The software may then be executed or stored for later execution.

Abstract: As an example, a computing device having a Unified Extensible Firmware Interface (UEFI) may boot into a preinstallation environment (associated with a first operating system), determine that a second operating system is to be installed on the computing device, and write an image of the second operating system to the boot disk. The image may include a special partition. The computing device may write the preinstallation environment (associated with first operating system) to the special partition of the image of the second operating system, and create a boot entry in the UEFI to cause the computing device to boot into the preinstallation environment (Windows PE). After booting into the preinstallation environment, the computing device may execute one or more diagnostic tests, delete the boot entry, and reboot the computing device to install a basic input output system (Coreboot) to replace UEFI and install the second operating system (Chrome OS).

Abstract: Described in detail herein is a profiling system. In one embodiment, a computing system can be configured to generate a graphical user interface through which a profiling application is configured, and receive a first request for initiating profiling of an executable module including one or more data structures via the graphical user interface. The computing system can further initiate the profiling of the executable module via the graphical user interface based on the information associated with the executable module, determine a first processor utilization and a first memory utilization during execution of the executable module, generate a first utilization snapshot from the first processor utilization and a first memory snapshot from the first memory utilization at a specified period of time during execution of the executable module, and store the first utilization and first memory snapshot in the database.

Abstract: According to some embodiments, methods and systems may be associated with an integration computing environment for an enterprise. An integration modeling design platform may receive, from an integration developer via a modeling notation, an indication that a retry component should be associated with an integration task. The integration modeling design platform may then configure the retry component for the integration task in connection with at least one of an integration adapter and an integration component (e.g., a selection of a messaging component, a quality of service, a retry period, an exponential back off option, etc.). According to some embodiments, an integration generation framework, coupled to the integration modeling design platform, may automatically construct an appropriate runtime retry representation based on the configured retry component (e.g., by creating a domain-specific language software component).

Abstract: An embodiment includes requesting, by a compiler responsive to execution of a first code segment, a first profile dataset associated with the first code segment. The embodiment also includes executing, responsive to receiving an indication that the first profile dataset is not available, a querying process that searches other code segments based on specified criteria relating to an attribute of the first code segment. The embodiment also includes receiving a search result from the querying process, where the search result includes a second code segment. The embodiment also includes generating an extrapolated profile dataset based at least in part on the second code segment. The embodiment stores the extrapolated profile dataset in memory associated with the first code segment, and the compiler performs an optimization process on the first code segment using the extrapolated profile dataset.

Abstract: A method may include generating, based on a first programming code implementing a routine in a first programming language, a second programming code implementing the routine in a second programming language associated with an offline runtime environment and a third programming code implementing the routine in a third programming language associated with an online runtime environment. The routine may include a first operation and a second operation associated with a cloud-based software application. The first operation may be capable of being performed while the cloud-based software application is operating in an offline mode but the second operation may be incapable of being performed while the cloud-based software application is operating in the offline mode. The second second programming code being generated to include the first operation and exclude the second operation. The second programming code and the third programming code may be deployed to a client.

Abstract: An open compiler system for the construction of safe and correct computational systems. This system allows a user to define multiple computational resources, each of which containing multiple computations, which, together, provide some desired functionality. This system generates the artifacts required to create such computational resources, may verify logical properties of such a system, may integrate user-defined programs in the process of compiling such artifacts, and may allow for the deployment, debugging, and monitoring of such computational resources.

Abstract: Systems and processes for prototyping and designing natively rendered multi-channel applications across diverse platforms are disclosed. The method of prototyping an application with a computing device includes providing a library of native design elements which are reproducible in different design layouts on an interface associated with different, predefined platforms. The method further includes converting a first design layout comprising one or more native design elements which fits within an interface associated with a first platform of the different, predefined platforms to a second design layout comprising the one or more native design elements which fits within an interface associated with a second platform of the different, predefined platforms, and which is in proportion to the first design layout.

Abstract: A method for modifying a call graph may include identifying, in source code, a first call site including a first predicate and a call from a first function to a second function. The first call site may correspond to a first edge of the call graph. The first edge may connect a first node corresponding to the first function and a second node corresponding to the second function. The method may further include modifying the call graph by labelling the first edge with a first encoding of the first predicate, and identifying, in the source code, a second call site including a second predicate and a call from a third function to the first function. The method may further include in response to determining that the first predicate is unsatisfied, modifying the call graph by labelling the second edge with a second encoding of a violation of the first predicate.