G06F11/362

Enabling Secure Debug Logging
20230229816 · 2023-07-20 ·

A software product that requires debugging receives a security token in response to a request to enable debug logging. The security token is validated. Upon a successful validation of the security token, debug logging is enabled and debug logs are encrypted while being dumped. A duration for which debug logging has been enabled is tracked. When the duration reaches a cutoff duration, the debug logging is disabled.

Pipelined micro controller unit

A 3D NAND memory device is provided in which control is performed by two microcontroller units (MCU). During manufacture of the memory device, bug fixes required for the controller may be addressed using a software solution by which an instruction requiring correction in one of the two MCUs is replaced with a corrected instruction stored in a RAM.

DELTA DEBUGGING METHOD AND SYSTEM BASED ON PROBABILITY MODEL

A delta debugging method and system based on a probability model which includes: acquiring an initial probability model and historical test data; optimizing and iterating the initial probability model through the historical test data to obtain an optimized and iterated probability model; and performing delta debugging on a target program containing multiple lines of code based on the optimized and iterated probability model to obtain a debugging result that meets a first preset condition. Therefore, by adopting the embodiment of the present application, the initial probability model can be continuously optimized and iterated through the historical test data, and the target program can be debugged based on the optimized and iterated probability model, so that the debugging result can be improved, or the compression amount of the size of the target program can reach a target compression amount, or the debugging time can be greatly reduced.

Telemetry targeted query injection for enhanced debugging in microservices architectures

An apparatus to facilitate telemetry targeted query injection for enhanced debugging in microservices architectures is disclosed. The apparatus includes one or more processors to: identify contextual trace of a previous query recorded in collected data of a service, where microservices of the service responded to the previous query; access an interdependency flow graph representing an architecture and interaction of microservices deployed for a service; retrieve, based on the interdependency flow graph, telemetry data of the microservices corresponding to the contextual trace; identify, based on the telemetry data, an activation profile corresponding to the previous query, the activation profile detailing a response of the microservices to the previous query; compare the activation profile to a correlation profile for the previous query to detect whether an anomaly occurred in the service in response to the previous query; and recommend a modified query based on detection of the anomaly.

Feedback framework

The present disclosure includes a feedback framework that receives feedback for a component of an information technology platform. The component includes the feedback framework, the information technology platform, a software application, a web browser, a client device, a client instance, or a virtual server. The feedback framework obtains context information associated with the feedback. The context information includes a system log, a screenshot, a web address of a web browser of the client device, version information, and/or the like. The feedback framework also determines an identity of the component by executing a handler. The feedback framework then determines a notification to send based on the identity of the component, and sends the notification with the feedback and the context information. In this manner, the feedback framework provides sufficient context information associated with the feedback to diagnose and address issues while delivering the feedback and context information quickly and efficiently.

Systems using computation graphs for flow solvers

An embodiment of a method can create a directed acyclic graph (DAG) from a programmer specified set of computation units to solve, in a computer program, physics based simulations of physical systems, and the DAG can be used to analyze and debug the computer program. In this method, the computer program can be created by automatically determining dependency relationships in the set of computation units and automatically schedule their execution. The method can also automatically allocate memory for the computation units.

Identifying root causes of software defects

Root cause identification of a software defect includes identifying, in program code of a software feature, hedge code of the software feature based on errors induced from temporarily substituting program code of the software feature with substitute program code and obtaining an error graph for the hedge code, obtaining error logs of an application that incorporates the software feature, the error logs indicating errors with the software feature of the application, automatically generating an application error graph reflective of the errors with the software feature of the application, mapping the application error graph to the error graph for the hedge code, and based on the mapping aligning one of more errors reflected in the application error graph to error(s) reflected in the error graph for the hedge code, identifying the hedge code as inducing a root error identified in the application error graph.

Method, System, and Computer Program Product for Operating Dynamic Shadow Testing Environments
20230214313 · 2023-07-06 ·

Described are a method, system, and computer program product for operating dynamic shadow testing environments for machine-learning models. The method includes generating a shadow testing environment operating at least two transaction services. The method also includes receiving a plurality of transaction authorization requests. The method further includes determining a first percentage associated with a first testing policy of the first transaction service and a second percentage associated with a second testing policy of the second transaction service. The method further includes replicating in the shadow testing environment, in real-time with processing the payment transactions, a first portion of the plurality of transaction authorization requests and a second portion of the plurality of transaction authorization requests. The method further includes testing the first transaction service using the first set of replicated transaction data and the second transaction service using the second set of replicated transaction data.

INFRASTRUCTURE TO INTEGRATE AN INTEGRATED DEVELOPMENT ENVIRONMENT (IDE) WITH GAME ENGINES

Techniques are described herein that are capable of integrating an IDE with game engines. States of the game engines are identified. Each state indicates whether the IDE enables a game developer to interact with the respective game engine and/or game(s) created by the respective game engine. A subset of the game engines is caused to be displayed to the game developer based at least in part on the IDE enabling the game developer to interact with each game engine in the subset and/or game(s) created by the respective game engine. A selection indicator, which indicates that a game engine is selected from the game engines in the subset, is received. An integration infrastructure, including a game engine-agnostic messaging protocol and game engine-agnostic messages, is provided. At least a portion of game code and/or test unit(s) are run and/or debugged using the IDE in a context of the selected game engine.

Visualization of code execution through line-of-code behavior and relation models
11694008 · 2023-07-04 · ·

Disclosed herein are techniques for visualizing and configuring controller function sequences. Techniques include identifying at least one executable code segment associated with a controller; analyzing the at least one executable code segment to determine at least one function and at least one functional relationship associated with the at least one code segment; constructing, a software functionality line-of-code behavior and relation model visually depicting the determined at least one function and at least one functional relationship; displaying the software functionality line-of-code behavior and relation model at a user interface; receiving a first input at the interface; in response to the received first input, animating the line-of-code behavior and relation model to visually depict execution of the at least one executable code segment on the controller; receiving a second input at the interface; and in response to the received second input, animating an update to the line-of-code behavior and relation model.