CN119690489A - A Java-based dynamic code hot replacement system and method - Google Patents
A Java-based dynamic code hot replacement system and method Download PDFInfo
- Publication number
- CN119690489A CN119690489A CN202411835580.6A CN202411835580A CN119690489A CN 119690489 A CN119690489 A CN 119690489A CN 202411835580 A CN202411835580 A CN 202411835580A CN 119690489 A CN119690489 A CN 119690489A
- Authority
- CN
- China
- Prior art keywords
- module
- code
- unit
- replacement
- hot
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a Java-based dynamic code hot replacement system and a Java-based dynamic code hot replacement method, wherein the system comprises a code management module, a hot replacement engine module, a CI/CD module and an error processing management module; the system comprises a code management module, a hot replacement engine module, a CI/CD module, an error processing management module and a user interface module, wherein the code management module is used for generating module metadata, the module metadata is used for guiding dependency analysis and conflict detection in a code replacement process, the hot replacement engine module is used for receiving module metadata, the hot replacement engine module is used for performing incremental replacement on codes, only replacing modified partial codes, realizing immediate effectiveness after the code replacement through deep integration with a JVM, the CI/CD module is used for managing continuous integration and continuous deployment processes of an application program, and the error processing management module is used for generating errors when the codes are subjected to incremental replacement and can automatically roll back to a previous version. The Java-based dynamic code hot replacing system and the Java-based dynamic code hot replacing method realize the support of JVM of different versions, and simultaneously ensure the stability of application performance and the simplification of development flow in the code replacing process.
Description
Technical Field
The embodiment of the invention relates to the field of business processing, in particular to a Java-based dynamic code hot replacement system and a Java-based dynamic code hot replacement method.
Background
Along with the rapid progress of the software development industry, the improvement of development efficiency and the acceleration of debugging speed have become key indexes for evaluating the advantages and disadvantages of development environments. In the traditional Java development scenario, if a modification needs to be made to an running application, the conventional flow is to stop the application first, and then recompile and deploy the updated code. This is time consuming and can cause disruption of service, especially for those services requiring 24 hours/7 days of uninterrupted operation.
In recent years, various development tools and frameworks are proposed in the industry, and hot replacement functions are introduced, so as to realize partial or complete updating of codes without suspending execution of application programs.
The invention patent with application number of CN202010216486.8 and name of 'an automatic management method facing Java class hot update' discloses an automatic management method facing Java class hot update, which comprises two parts of class hot update execution and class hot update history inquiry, wherein the class hot update execution comprises the following steps of step 1, selecting a class to be subjected to hot update, identifying a class file path, converting the path into a software package path, returning the software package path for user confirmation, automatically modifying the path into a correct software package path by the user if the automatically identified path is wrong, executing step 2, otherwise directly executing step 2, clearing a compiling catalog, copying a class file to be replaced to the compiling catalog, automatically generating a catalog structure identical with the software package path, step 3, firstly searching whether a target process has a hot replacement log, if so, reading the log, determining a new sequence number for the class to be updated, setting the sequence number of the class to be updated to be 0, then modifying the class to be subjected to the hot update package path according to the sequence number, step 4, placing javac in the compiling catalog, writing the compiling command into the compiling catalog to be subjected to the target process, and carrying out the step 5, and inquiring the target process by the hot update catalog, and carrying out the step 1, and the step 1, the step 1 is carried out a hot update, and the step 1 is carried out a hot update-copy, and the target process is carried out by a hot-copy record, and a hot-copy record is searched, and searching the log file according to the pid, analyzing and presenting the history record in the log to the user. However, the above-described methods are relatively complex and inefficient in particular use.
To this end, there is a need to provide a Java-based dynamic code hot-swap system and method to solve the above-mentioned problems.
Disclosure of Invention
The embodiment of the application aims to provide a Java-based dynamic code hot replacing system and a Java-based dynamic code hot replacing method, which realize the support of JVM of different versions and ensure the stability of application performance and the simplification of development flow in the process of code replacement.
According to one aspect of the present invention, there is provided a Java-based dynamic code hot-swap system, which includes a code management module, a hot-swap engine module, a CI/CD module, and an error handling management module;
The code management module is used for generating module metadata, and the module metadata is used for guiding the dependency analysis and conflict detection in the code replacement process;
The hot replacement engine module receives the module metadata, and is used for performing incremental replacement on codes, replacing only modified partial codes, and realizing immediate effectiveness after code replacement through deep integration with the JVM;
the CI/CD module is used for managing the continuous integration and continuous deployment process of the application program, including automatic construction, test, packaging and deployment;
the error processing management module is used for generating errors when the codes are subjected to incremental replacement, and can automatically roll back to the previous version.
Preferably, the code management module comprises a code module management unit, a metadata generation unit, a dependency management unit and a version management unit;
The code module management unit is used for loading, unloading and updating the code module, and deploying the code module into the running environment when a new code version is detected;
The metadata generation unit is used for generating metadata describing the structure and the behavior of the code module management unit for the code module management unit, wherein the structure comprises classes, methods and attributes, and the behavior comprises an entry point and a callback mechanism;
The dependency management unit is used for automatically analyzing the dependency relationship of the module, transmitting the dependency relationship to the hot replacement engine module, and automatically updating the related dependency module by the hot replacement engine module according to the dependency relationship to ensure the consistency of the dependency relationship;
The version management unit is used for tracking different versions of codes, providing the capability of version rollback and supporting coexistence of parallel versions.
Preferably, the hot replacement engine module comprises a byte code operation library, a class loader management unit, an event monitoring unit and a notification mechanism unit;
the byte code operation library is used for reading, modifying and generating Java byte codes;
The class loader management unit is used for managing and coordinating the behavior of the class loader to ensure that the class with the new version can be loaded correctly and replace the old version, and is also used for processing class unloading so as to avoid memory leakage;
the event listening unit is configured to monitor class loading, unloading and other critical events that may affect the hot replacement process. The method can register a monitor, and when a specific event occurs, a corresponding callback function is called;
The notification mechanism unit is used for reporting information in the hot replacement process, wherein the information comprises successful update, error occurrence and rollback operation, and the information is realized by means of log record, mail transmission and instant messaging.
Preferably, the CI/CD module comprises a construction automation unit, an automation deployment unit and a dynamic code hot replacement unit;
The construction automation unit is used for automatically compiling source codes, running unit testing, integration testing and packaging to generate deployable workpieces, wherein the deployable workpieces comprise JAR files and WAR files;
The automatic deployment unit is used for managing the deployment process of the application program and comprises the steps of uploading a construction product to a target server, configuring environment variables and starting or restarting services;
the dynamic code hot replacing unit is used for carrying out code updating when the application program runs, and the code updating comprises class loader management, byte code operation, event monitoring and notification mechanisms.
Preferably, the error processing management module comprises an error detection unit, an error report notification unit and a rollback mechanism unit;
the error detection unit is used for monitoring the running state of the application program in real time, identifying and capturing the abnormality and the error, wherein the identifying and capturing the abnormality and the error comprises analysis of log files, capturing of abnormal stack tracking and monitoring of performance indexes;
The error report notification unit is used for generating a detailed error report when an abnormal situation is found, and sending out notification through various channels, wherein the error report comprises error description, occurrence time, influence range and preliminary diagnosis information, and the various channels comprise mail, instant message and log record;
The rollback mechanism unit is configured to restore the application program to a previous stable version when a serious error or a hot replacement failure is detected, where restoring the application program to the previous stable version includes unloading a new version class, reloading an old version class, and performing a cleanup operation, where the cleanup operation includes cleaning a cache and resetting a database connection.
Preferably, the system further comprises a log monitoring module for capturing, filtering and analyzing log information of the application program in real time, wherein the log information comprises a log file, a log level and keywords, and the log monitoring module is ELK Stack, splunk, graylog, log, 4J2 or SLF4J.
Preferably, the system further comprises an input interface module provided with a real unit, a Vue unit, an Echarts unit, a Material-UI unit, a CSS unit and an HTML unit;
the act unit is used for constructing a user interface and providing a declarative programming mode;
The Vue unit is used for constructing a user interface and providing a progressive JavaScript framework;
the Echarts unit is used for performing data visualization and providing chart types and configuration options;
The Material-UI unit is used for quickly constructing a user interface conforming to the Google MATERIAL DESIGN specification;
The CSS unit is used for defining and managing style rules;
the HTML unit is used to define the layout and content of the page, providing semantic tags.
Preferably, the automatically updating the related dependency module according to the dependency relationship specifically includes:
when the dependency relationship is a first dependency relationship, downloading a first application program package to update a related dependency module;
when the dependency relationship is a second dependency relationship, downloading a second application program package to update the related dependency module;
and storing the first dependency relationship and the second dependency relationship in a first tree structure and a second tree structure respectively.
Preferably, a signature file is added in the first application program package or the second application program package, a first hash algorithm is used for calculating the signature file, a second hash algorithm is used for calculating a hash value of the signature file, the hash value is mapped to the end-to-end hash ring virtual node, the first hash algorithm is a static hash algorithm, and the second hash algorithm is an elastic hash algorithm.
According to another aspect of the present invention, there is provided a Java-based dynamic code hot-swapping method, the method comprising:
Guiding the dependency parsing and conflict detection in the code replacement process;
Incremental replacement is carried out on codes, only modified partial codes are replaced, and the codes are immediately effective after replacement through deep integration with the JVM;
managing a continuous integration and continuous deployment process of an application program, including automated construction, testing, packaging, and deployment;
Errors occur when the code is incrementally replaced, enabling automatic rollback to the previous version.
The application discloses a Java-based dynamic code hot replacement system and a Java-based dynamic code hot replacement method, wherein the system comprises a code management module, a hot replacement engine module, a CI/CD module and an error processing management module, wherein the code management module is used for generating module metadata, the module metadata is used for guiding dependency analysis and conflict detection in a code replacement process, the hot replacement engine module is used for carrying out incremental replacement on codes, only replacing part of modified codes, realizing immediate effectiveness after the code replacement through deep integration with a JVM, and the CI/CD module is used for managing the continuous integration and continuous deployment process of an application program, including automatic construction, testing, packaging and deployment, and the error processing management module is used for generating errors when the codes are subjected to incremental replacement, automatically rolling back to previous versions, realizing support on different versions of the JVM, and simultaneously ensuring stability of application performance and simplification of development flow in the code replacement process;
Further, when the dependency relationship is a first dependency relationship, downloading a first application program package to update a related dependency module; when the dependency relationship is a second dependency relationship, downloading a second application program package to update related dependency modules, respectively storing the first dependency relationship and the second dependency relationship in a first tree structure and a second tree structure, and downloading the first application program package or the second application program package by using the first dependency relationship and the second dependency relationship, thereby improving the updating efficiency of the application program package;
Further, signature files are added in the first application program package or the second application program package, the signature files are calculated by using a first hash algorithm, hash values of the signature files are calculated by using a second hash algorithm, the hash values are mapped to end-to-end hash ring virtual nodes, the first hash algorithm is a static hash algorithm, the second hash algorithm is an elastic hash algorithm, and the signature files are checked by using the first hash algorithm and the second hash algorithm, so that safe updating of the first application program package or the second application program package is ensured.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the prior art, a brief description of the drawings is provided below, wherein it is apparent that the drawings in the following description are some, but not all, embodiments of the present invention. Other figures may be derived from these figures without inventive effort for a person of ordinary skill in the art.
FIG. 1 is a block diagram of a Java-based dynamic code hot-swap system according to embodiments of the present invention;
fig. 2 is a flow diagram of a Java-based dynamic code hot-swapping method according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.
The technical scheme of the invention is described in detail below by specific examples. The following embodiments may be combined with each other, and some embodiments may not be repeated for the same or similar concepts or processes.
According to the problems existing in the prior art, the embodiment of the invention provides a Java-based dynamic code hot replacing system and a Java-based dynamic code hot replacing method, which realize the support of JVM of different versions and simultaneously ensure the stability of application performance and the simplification of development flow in the code replacing process.
FIG. 1 is a schematic block diagram of a Java-based dynamic code hot-swap system according to an embodiment of the present invention, where, as shown in FIG. 1, the Java-based dynamic code hot-swap system provided in the embodiment of the present invention includes a code management module, a hot-swap engine module, a CI/CD module, and an error handling management module;
The code management module is used for generating module metadata, and the module metadata is used for guiding the dependency analysis and conflict detection in the code replacement process;
The hot replacement engine module receives the module metadata, and is used for performing incremental replacement on codes, replacing only modified partial codes, and realizing immediate effectiveness after code replacement through deep integration with the JVM;
the CI/CD module is used for managing the continuous integration and continuous deployment process of the application program, including automatic construction, test, packaging and deployment;
the error processing management module is used for generating errors when the codes are subjected to incremental replacement, and can automatically roll back to the previous version.
Preferably, the code management module comprises a code module management unit, a metadata generation unit, a dependency management unit and a version management unit;
The code module management unit is used for loading, unloading and updating the code module, and deploying the code module into the running environment when a new code version is detected;
The metadata generation unit is used for generating metadata describing the structure and the behavior of the code module management unit for the code module management unit, wherein the structure comprises classes, methods and attributes, and the behavior comprises an entry point and a callback mechanism;
The dependency management unit is used for automatically analyzing the dependency relationship of the module, transmitting the dependency relationship to the hot replacement engine module, and automatically updating the related dependency module by the hot replacement engine module according to the dependency relationship to ensure the consistency of the dependency relationship;
The version management unit is used for tracking different versions of codes, providing the capability of version rollback and supporting coexistence of parallel versions.
In specific implementation, the hot replacement engine module comprises a byte code operation library, a class loader management unit, an event monitoring unit and a notification mechanism unit;
the byte code operation library is used for reading, modifying and generating Java byte codes;
The class loader management unit is used for managing and coordinating the behavior of the class loader to ensure that the class with the new version can be loaded correctly and replace the old version, and is also used for processing class unloading so as to avoid memory leakage;
the event listening unit is configured to monitor class loading, unloading and other critical events that may affect the hot replacement process. The method can register a monitor, and when a specific event occurs, a corresponding callback function is called;
The notification mechanism unit is used for reporting information in the hot replacement process, wherein the information comprises successful update, error occurrence and rollback operation, and the information is realized by means of log record, mail transmission and instant messaging.
In a specific implementation, the CI/CD module comprises a construction automation unit, an automation deployment unit and a dynamic code hot replacement unit;
The construction automation unit is used for automatically compiling source codes, running unit testing, integration testing and packaging to generate deployable workpieces, wherein the deployable workpieces comprise JAR files and WAR files;
The automatic deployment unit is used for managing the deployment process of the application program and comprises the steps of uploading a construction product to a target server, configuring environment variables and starting or restarting services;
the dynamic code hot replacing unit is used for carrying out code updating when the application program runs, and the code updating comprises class loader management, byte code operation, event monitoring and notification mechanisms.
In specific implementation, the error processing management module comprises an error detection unit, an error report notification unit and a rollback mechanism unit;
the error detection unit is used for monitoring the running state of the application program in real time, identifying and capturing the abnormality and the error, wherein the identifying and capturing the abnormality and the error comprises analysis of log files, capturing of abnormal stack tracking and monitoring of performance indexes;
The error report notification unit is used for generating a detailed error report when an abnormal situation is found, and sending out notification through various channels, wherein the error report comprises error description, occurrence time, influence range and preliminary diagnosis information, and the various channels comprise mail, instant message and log record;
The rollback mechanism unit is configured to restore the application program to a previous stable version when a serious error or a hot replacement failure is detected, where restoring the application program to the previous stable version includes unloading a new version class, reloading an old version class, and performing a cleanup operation, where the cleanup operation includes cleaning a cache and resetting a database connection.
In a specific implementation, the system further comprises a log monitoring module, which is used for capturing, filtering and analyzing log information of the application program in real time, wherein the log information comprises a log file, a log level and a keyword, and the log monitoring module is ELK Stack, splunk, graylog, log J2 or SLF4J.
In a specific implementation, the system further comprises an input interface module, wherein the input interface module is provided with a real unit, a Vue unit, an Echarts unit, a Material-UI unit, a CSS unit and an HTML unit;
the act unit is used for constructing a user interface and providing a declarative programming mode;
The Vue unit is used for constructing a user interface and providing a progressive JavaScript framework;
the Echarts unit is used for performing data visualization and providing chart types and configuration options;
The Material-UI unit is used for quickly constructing a user interface conforming to the Google MATERIAL DESIGN specification;
The CSS unit is used for defining and managing style rules;
the HTML unit is used to define the layout and content of the page, providing semantic tags.
In a specific implementation, the automatic updating of the related dependency module according to the dependency relationship specifically includes:
when the dependency relationship is a first dependency relationship, downloading a first application program package to update a related dependency module;
when the dependency relationship is a second dependency relationship, downloading a second application program package to update the related dependency module;
and storing the first dependency relationship and the second dependency relationship in a first tree structure and a second tree structure respectively.
In specific implementation, a signature file is added in the first application program package or the second application program package, the signature file is calculated by using a first hash algorithm, a hash value of the signature file is calculated by using a second hash algorithm, the hash value is mapped to an end-to-end hash ring virtual node, the first hash algorithm is a static hash algorithm, and the second hash algorithm is an elastic hash algorithm.
Fig. 2 is a flow chart of a Java-based dynamic code hot replacing method according to an embodiment of the present invention, as shown in fig. 2, the method includes:
Step S201, guiding the dependency resolution and conflict detection in the code replacement process;
Step S202, performing incremental replacement on codes, replacing only part of modified codes, and realizing immediate effectiveness after the replacement of the codes through deep integration with the JVM;
Step 203, managing the continuous integration and continuous deployment process of the application program, including automatic construction, test, packaging and deployment;
step S204, when the code is subjected to incremental replacement, an error occurs, and the code can be automatically rolled back to the previous version.
The following specifically exemplifies the Java-based dynamic code hot-replacement method described above:
1. User request:
A user accesses the front-end interface of the system through a browser and loads pages containing React, vue, echarts, material-UI, CSS and HTML.
2. Initializing:
After the page loading is completed, the fact or Vue framework is initialized, and an initial user interface is rendered. The Material-UI component library is used to build interface elements, and the Echarts chart is rendered according to the initial data.
3. User interaction:
the user interacts with the interface such as clicking on a button, selecting an option, entering text, etc. The act or Vue component captures these events and updates the local state or sends requests to the backend as needed.
4. Data acquisition and updating:
The act or Vue component may initiate an API request if data needs to be obtained from the back-end. Upon receiving the response, the component updates the state and re-renders the relevant portion. For the Echarts chart, the data update triggers a redraw of the chart.
5. Error handling:
If an error occurs in the interaction process, the error detection unit captures the abnormality, the error report notification unit generates a detailed error report, and the log monitoring module records the related information. Friendly error cues can be displayed on the user interface.
6. Thermal replacement feedback:
When dynamic code hot replacement occurs, the front-end interface can receive update notifications through WebSocket or other real-time communication mechanisms. The exact or Vue component can be reloaded according to the new code version without refreshing the entire page. The echartists graph can be automatically updated according to new data sources.
7. Rollback and recovery:
The rollback mechanism unit may trigger a rollback operation if the hot replacement fails or a problem occurs. The front-end interface will receive the rollback notification and update the state and view accordingly, ensuring that the user always sees the latest stable version.
8. And (3) performance monitoring:
the log monitoring module not only monitors the back-end log, but also can collect front-end performance indexes such as loading time and response time. These data can help optimize front-end performance, ensuring a smooth user experience.
In summary, the system comprises a code management module, a hot replacement engine module, a CI/CD module and an error processing management module, wherein the code management module is used for generating module metadata, the module metadata is used for guiding the analysis of dependence and the detection of conflict in the process of replacing codes, the hot replacement engine module is used for carrying out incremental replacement on codes, only replacing modified partial codes, realizing immediate effectiveness after the replacement of codes through deep integration with JVM, the CI/CD module is used for managing the continuous integration and continuous deployment process of application programs, including automatic construction, test, packaging and deployment, and the error processing management module is used for carrying out errors when the codes are subjected to incremental replacement, automatically rolling back to the previous version, realizing the support of different versions of JVM, and simultaneously ensuring the stability of application performance and the simplification of development flow in the process of replacing codes;
Further, when the dependency relationship is a first dependency relationship, downloading a first application program package to update a related dependency module; when the dependency relationship is a second dependency relationship, downloading a second application program package to update related dependency modules, respectively storing the first dependency relationship and the second dependency relationship in a first tree structure and a second tree structure, and downloading the first application program package or the second application program package by using the first dependency relationship and the second dependency relationship, thereby improving the updating efficiency of the application program package;
Further, signature files are added in the first application program package or the second application program package, the signature files are calculated by using a first hash algorithm, hash values of the signature files are calculated by using a second hash algorithm, the hash values are mapped to end-to-end hash ring virtual nodes, the first hash algorithm is a static hash algorithm, the second hash algorithm is an elastic hash algorithm, and the signature files are checked by using the first hash algorithm and the second hash algorithm, so that safe updating of the first application program package or the second application program package is ensured.
It should be noted that the above embodiments are merely for illustrating the technical solution of the present invention and not for limiting the same, and although the present invention has been described in detail with reference to the above embodiments, it should be understood by those skilled in the art that the technical solution described in the above embodiments may be modified or some or all of the technical features may be equivalently replaced, and these modifications or substitutions do not make the essence of the corresponding technical solution deviate from the scope of the technical solution of the embodiments of the present invention.
Claims (10)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202411835580.6A CN119690489A (en) | 2024-12-13 | 2024-12-13 | A Java-based dynamic code hot replacement system and method |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202411835580.6A CN119690489A (en) | 2024-12-13 | 2024-12-13 | A Java-based dynamic code hot replacement system and method |
Publications (1)
Publication Number | Publication Date |
---|---|
CN119690489A true CN119690489A (en) | 2025-03-25 |
Family
ID=95044498
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202411835580.6A Pending CN119690489A (en) | 2024-12-13 | 2024-12-13 | A Java-based dynamic code hot replacement system and method |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN119690489A (en) |
-
2024
- 2024-12-13 CN CN202411835580.6A patent/CN119690489A/en active Pending
Similar Documents
Publication | Publication Date | Title |
---|---|---|
Tomassi et al. | Bugswarm: Mining and continuously growing a dataset of reproducible failures and fixes | |
US12353319B2 (en) | Scalable execution tracing for large program codebases | |
EP3769223B1 (en) | Unified test automation system | |
US9740594B2 (en) | Automated debug trace specification | |
CN110554965B (en) | Automated fuzz testing method, related equipment and computer readable storage medium | |
US7698691B2 (en) | Server application state | |
US20100185590A1 (en) | Autonomic information management system (ims) mainframe database pointer error diagnostic data extraction | |
US9588872B2 (en) | Discovery of code paths | |
CN112099880A (en) | Scenario-driven application reduction method and system | |
Dai et al. | Dscope: Detecting real-world data corruption hang bugs in cloud server systems | |
CN112506923B (en) | Method, device and electronic device for determining link of method call corresponding to business | |
CN111352631A (en) | Interface compatibility detection method and device | |
Nguyen et al. | An empirical study of exception handling bugs and fixes | |
CN119690489A (en) | A Java-based dynamic code hot replacement system and method | |
CN111367796A (en) | Application program debugging method and device | |
CN119862167B (en) | File operation tracking method and device, computer equipment and storage medium | |
WO2020194000A1 (en) | Method of detecting and removing defects | |
CN119357161B (en) | Pre-data construction method, device, storage medium and program product | |
CN107632934B (en) | Function copying method and device in C-sharp | |
Ross et al. | Exception monitoring for the Flask Monitoring Dashboard | |
嶋利 et al. | Study on Cost-Effective Debugging Methods under | |
Jin | Understanding and Detecting Software Upgrade Failures in Distributed Systems | |
CN119829407A (en) | Program debugging method and device | |
CN119149403A (en) | Application program testing method, device, equipment, storage medium and program product | |
CN118916076A (en) | Version injection method, version injection device, electronic equipment, storage medium and product |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination |