CN111240873A - Code error record management method and device - Google Patents
Code error record management method and device Download PDFInfo
- Publication number
- CN111240873A CN111240873A CN201911414123.9A CN201911414123A CN111240873A CN 111240873 A CN111240873 A CN 111240873A CN 201911414123 A CN201911414123 A CN 201911414123A CN 111240873 A CN111240873 A CN 111240873A
- Authority
- CN
- China
- Prior art keywords
- code
- error
- error record
- submission
- information
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0787—Storage of error reports, e.g. persistent data storage, storage using memory protection
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a code error record management method and a device, and the method and the device can obtain a code trace of an error code generating the error record after receiving the error record, and can fully know all relevant code files related to the error code and the line number of the relevant code; the method comprises the steps of analyzing a code trace to obtain a plurality of information items, processing the information items and extracting historical code submitting information, wherein the historical code submitting information records all submitting time and names of submitters, the name of the last submitter of a related code line number can be found in the historical code submitting information, and finally an error record is sent to the last submitter.
Description
Technical Field
The present application relates to the field of computer network technologies, and in particular, to a method and an apparatus for managing code error records.
Background
In the field of software development, errors often exist in codes submitted by programmers, the types of the errors are generally two, one is that the submitted codes do not conform to code specifications specified by organization unification, and the quality of the whole codes is reduced; the other method is that the submitted code can generate errors in the software running process, so that the software cannot run in a preset mode. Therefore, the codes submitted by programmers need to be managed, and the influence of error codes on software operation is prevented.
In the prior art, after software runs, when an error code causes a problem in software running, an error record causing the problem in software running is reported to a server, and then all programmers periodically search a record page for an error record related to a code submitted by themselves to modify the submitted code. However, the programmer is required to periodically search for the error record associated with the programmer, so that the error code cannot be processed in time.
Disclosure of Invention
In view of the above, the present application provides a method and an apparatus for managing a code error record, which solve the technical problem that an error code cannot be processed in time due to the fact that a programmer needs to search for an error record related to the programmer at regular time.
A first aspect of the present application provides a code error record management method, including:
acquiring an error record, and recording a corresponding code resource version number generating the error record as a first version number, wherein the error record is a software operation error caused by an error code;
obtaining a code trace based on the error record, wherein the code trace comprises names of all relevant code files relevant to the error code and a line number where the relevant code is located;
analyzing the code trace to obtain a plurality of information items, wherein each information item comprises a name of the related code file and a related code line number;
processing the plurality of information items, and extracting historical code submission information of the relevant code file relative to the first version number;
obtaining the name of the last submitter of the line number of the related code according to the historical code submission information;
sending the error record to the last submitter.
Optionally, the obtaining an error record, recording a version number of a corresponding code resource generating the error record as a first version number, and recording the error record as a software operation error caused by an error code, and then obtaining a code trace based on the error record, before further comprising:
generating an ID number by using an MD5 algorithm according to the error record;
and searching whether the ID number exists in an ID library, if so, acquiring the name of a submitter corresponding to the ID number, and sending the error record to the submitter, otherwise, adding the ID number to the ID library.
Optionally, the processing the plurality of information items, and extracting historical code submission information of the relevant code file relative to the first version number, includes:
and extracting the name of the related code file in the information item, and extracting historical code submission information of the related code file relative to the first version number by using a command in code submission version management software.
Optionally, the obtaining, according to the historical code submission information, the name of the last submitter of the relevant code line number includes:
obtaining all submission times of the relevant code line number according to the historical code submission information;
sequencing all submission times of the relevant code line numbers in the historical code submission information to obtain the final submission time;
and obtaining the name of the last submitter according to the last submission time.
Optionally, the sending the error record to the last submitter includes:
sending the error record to the last submitter by way of mail.
A second aspect of the present application provides a code error record management apparatus, including:
the device comprises an acquisition recording unit, a processing unit and a processing unit, wherein the acquisition recording unit is used for acquiring an error record and recording a corresponding code resource version number generating the error record as a first version number, and the error record is a software operation error caused by an error code;
the obtaining unit is used for obtaining a code trace based on the error record, wherein the code trace comprises the names of all relevant code files relevant to the error code and the line number of the relevant code;
the analysis unit is used for analyzing the code trace to obtain a plurality of information items, and each information item comprises the name of the related code file and a related code line number;
the processing unit is used for processing the plurality of information items and extracting historical code submission information of the related code file relative to the first version number;
the information integration unit is used for obtaining the name of the last submitter of the relevant code line number according to the historical code submission information;
a sending unit, configured to send the error record to the last submitter.
Optionally, the method further comprises:
a generating unit, for generating an ID number by using MD5 algorithm according to the error record;
and the searching unit is used for searching whether the ID number exists in an ID library, if so, acquiring the name of a submitter corresponding to the ID number, sending the error record to the submitter, and if not, adding the ID number to the ID library.
Optionally, the processing unit is specifically configured to;
and extracting the name of the related code file in the information item, and extracting historical code submission information of the related code file relative to the first version number by using a command in code submission version management software.
Optionally, the information integrating unit includes:
the time acquisition unit is used for acquiring all submission times of the relevant code line number according to the historical code submission information;
the sequencing unit is used for sequencing all the submission times of the relevant code line numbers in the historical code submission information to obtain the final submission time;
and the name obtaining unit is used for obtaining the name of the last submitter according to the last submission time.
Optionally, the sending unit is specifically configured to:
sending the error record to the last submitter by way of mail.
According to the technical scheme, the method has the following advantages:
the application provides a code error record management method, which comprises the following steps: acquiring an error record, and recording the version number of a corresponding code resource generating the error record as a first version number, wherein the error record is a software operation error caused by an error code; obtaining a code trace based on the error record, wherein the code trace comprises the names of all relevant code files relevant to the error code and the line number of the relevant code; analyzing the code trace to obtain a plurality of information items, wherein each information item comprises the name of a related code file and a related code line number; processing the plurality of information items, and extracting historical code submission information of the relevant code file relative to the first version number; obtaining the name of the last submitter of the relevant code line number according to the historical code submission information; the error record is sent to the last submitter.
After the error record is received, the code trace of the error code generating the error record is obtained, and all relevant code files relevant to the error code and the line number where the relevant code is located can be fully known; the method comprises the steps of analyzing a code trace to obtain a plurality of information items, processing the information items and extracting historical code submitting information, wherein the historical code submitting information records all submitting time and names of submitters, the name of the last submitter of a related code line number can be found in the historical code submitting information, and finally an error record is sent to the last submitter.
Drawings
FIG. 1 is a flowchart illustrating a code error record management method according to an embodiment of the present application;
FIG. 2 is a schematic flow chart illustrating a code error record management method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an embodiment of a code error record management apparatus in an embodiment of the present application.
Detailed Description
There are three methods for improving the software operation failure caused by the error code. The first method is that before the code is submitted, a programmer detects partial code errors by a static code detection tool, but the method can only detect some codes which do not meet the code specification or some simpler errors; secondly, after the codes are submitted and before the software runs, more experienced programmers are dispatched to examine the submitted codes, so that the more experienced programmers are needed, and more labor cost is consumed; and thirdly, after the software runs, when the error code causes the software to run to have a problem, reporting the error record causing the software to run to the server, then all programmers periodically search the error record related to the code submitted by the programmers on the recording page to modify the submitted code, however, the programmers need to check the error record one by one on the recording page at regular time, so that the working efficiency is greatly reduced, the error code cannot be processed in time, and when the error record is more, the problem that the programmers neglect to process the error record related to the programmers can exist.
In view of this, the embodiments of the present application provide a method and an apparatus for managing a code error record, which solve the technical problem that an error code cannot be processed in time due to the fact that a programmer needs to search for an error record associated with the programmer at regular time.
In order to make the objects, features and advantages of the present invention more apparent and understandable, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the embodiments described below are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, an embodiment of the present application provides a method for managing a code error record, including:
step S101, obtaining error records, and recording the version number of the corresponding code resource generating the error records as a first version number, wherein the error records are software operation errors caused by error codes.
It should be noted that a group of codes is modified by a programmer and submitted to a server to generate a version, for example, a modifies the codes and submits to the server for storage to generate a code version called 1001, and b modifies the group of codes and submits to the server to generate a code version called 1002, when an error code causes a software operation error, an error record is generated, the software version number used by a user is different from the version number used by the programmer, and the software operation error generally occurs when the user uses the software, so the corresponding code resource version number generating the error code needs to be recorded.
And S102, acquiring a code trace based on the error record, wherein the code trace comprises the names of all relevant code files relevant to the error code and the line number of the relevant code.
It should be noted that the code trace refers to a file in which the code related to the error code is located and a line number of the related code in the file.
Step S103, analyzing the code trace to obtain a plurality of information items, wherein each information item comprises a name of a related code file and a related code line number.
And step S104, processing the plurality of information items, and extracting historical code submission information of the relevant code file relative to the first version number.
It should be noted that a new version number is regenerated after a group of codes is modified, and therefore, when extracting the history code submission information of an error code, the first version number that generates the error code and the history code submission information before the first version number need to be extracted.
And step S105, obtaining the name of the last submitter of the relevant code line number according to the historical code submission information.
And step S106, sending the error record to the last submitter.
After the error record is received, the code trace of the error code generating the error record is obtained, and all relevant code files relevant to the error code and the line number where the relevant code is located can be fully known; the method comprises the steps of analyzing a code trace to obtain a plurality of information items, processing the information items and extracting historical code submitting information, wherein the historical code submitting information records all submitting time and names of submitters, the name of the last submitter of a related code line number can be found in the historical code submitting information, and finally an error record is sent to the last submitter.
The above is a detailed description of a first embodiment of a code error record management method provided by the present application, and the following is a detailed description of a second embodiment of a code error record management method provided by the present application
Referring to fig. 2, an embodiment of the present application provides a method for managing a code error record, including:
step S201, obtaining an error record, and recording that the version number of a corresponding code resource generating the error record is a first version number, and the error record is a software operation error caused by an error code.
Step S202, based on the error record, an ID number is generated by using an MD5 algorithm.
It can be understood that the ID refers to an erroneous identification number, because software may be used by many users at the same time, and an error may be triggered by many users, the same error may be triggered many times, resulting in many error records, in order to avoid repeated processing of the same error record, an ID number is assigned to the error record, a correspondence between the error record and the ID number is established, one error record corresponds to one ID number, the same error record may have the same ID number, different error records, and different ID numbers.
Step S203, searching whether the ID number exists in the ID library, if so, acquiring the name of the submitter corresponding to the ID number, sending the error record to the submitter, and if not, adding the ID number to the ID library.
It should be noted that, if the ID number already exists, it indicates that the error record has already been processed, and no further processing is needed, and the name of the submitter corresponding to the ID number is to be acquired, and the error record is sent to the submitter, and if the ID does not exist, the ID number is added to the ID library, and the processing is continued.
And S204, acquiring a code trace based on the error record, wherein the code trace comprises the names of all relevant code files relevant to the error code and the line number of the relevant code.
Step S205, analyzing the code trace to obtain a plurality of information items, wherein each information item comprises a name of a related code file and a related code line number.
And S206, extracting the name of the related code file in the information item, and extracting the historical code submission information of the related code file relative to the first version number by using a command in the code submission version management software.
And step S207, obtaining all submission time of the relevant code line number according to the historical code submission information.
It should be noted that, submitting a code correspondingly generates a time, and the historical code submitting information includes the time of a related code file and the time of a related code line number, while a file may be modified by many people, the last submitter of the file is not necessarily the submitter of an error record, and the error record is generally caused by which line code or which line code in the file, so that the submitting time of the related code line number needs to be accurately obtained.
And S208, sequencing all the submission times of the relevant code line numbers in the historical code submission information to obtain the final submission time.
It should be noted that all the commit times of the relevant code line numbers are sorted, the times are sorted from front to back, and the last commit time of the relevant code line numbers can be obtained.
And step S209, obtaining the name of the last submitter according to the last submission time.
Step S210, sending the error record to the last submitter by way of mail.
It should be noted that, besides the mail, the person skilled in the art can also set up to send the error record to the last submitter through communication software such as mobile phone message, WeChat, qq or nail.
After the error record is received, the code trace of the error code generating the error record is obtained, and all relevant code files relevant to the error code and the line number where the relevant code is located can be fully known; the method comprises the steps of analyzing a code trace to obtain a plurality of information items, processing the information items and extracting historical code submission information, wherein the historical code submission information records all submission times and names of submitters, the submission times are sequenced to obtain the final submission time, the name of the final submitter of a related code line number can be found in the historical code submission information according to the final submission time, and finally an error record is sent to the final submitter.
The above is a detailed description of a second embodiment of a code error record management method provided by the present application, and the following is a detailed description of an embodiment of a code error record management apparatus provided by the present application.
Referring to fig. 3, an embodiment of the present application provides a code error record management apparatus, including:
the acquiring and recording unit 301 is configured to acquire an error record, and record a version number of a corresponding code resource that generates the error record as a first version number, where the error record is a software operation error caused by an error code.
A generating unit 302 for generating an ID number using an MD5 algorithm according to the error record;
the searching unit 303 is configured to search whether the ID number exists in the ID library, if so, obtain the name of the submitter corresponding to the ID number, and send the error record to the submitter, and if not, add the ID number to the ID library.
An obtaining unit 304, configured to obtain a code trace based on the error record, where the code trace includes names of all relevant code files related to the error code and a line number where the relevant code is located.
The analyzing unit 305 is configured to analyze the code trace to obtain a plurality of information items, where each information item includes a name of an associated code file and an associated code line number.
And the processing unit 306 is used for processing the plurality of information items and extracting the historical code submission information of the relevant code file relative to the first version number.
It should be noted that the processing unit 306 is specifically configured to extract the name of the relevant code file in the information item, and extract the historical code submission information of the relevant code file relative to the first version number by using a command in the code submission version management software.
And an information integration unit 307, configured to obtain the name of the last submitter of the relevant code line number according to the historical code submission information.
Note that the information integrating unit 307 includes an acquisition time unit 3071, a ranking unit 3072, and an acquisition name unit 3073.
The get time unit 3071 is used to get all the submission times of the relevant code line numbers according to the historical code submission information.
The sorting unit 3072 is configured to perform sorting processing on all submission times of the relevant code line numbers in the historical code submission information to obtain a final submission time.
The get name unit 3073 is used to get the name of the last submitter according to the last submission time.
A sending unit 308 for sending the error record to the last submitter.
It should be noted that the sending unit 308 is specifically configured to send the error record to the last submitter by way of mail, and besides mail, a person skilled in the art may also set to send the error record to the last submitter by way of communication software such as mobile phone information, WeChat, qq, or nailing.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the network, the apparatus and the unit described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the units is only one logical functional division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another grid network to be installed, or some features may be omitted or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (10)
1. A code error log management method, comprising:
acquiring an error record, and recording a corresponding code resource version number generating the error record as a first version number, wherein the error record is a software operation error caused by an error code;
obtaining a code trace based on the error record, wherein the code trace comprises names of all relevant code files relevant to the error code and a line number where the relevant code is located;
analyzing the code trace to obtain a plurality of information items, wherein each information item comprises a name of the related code file and a related code line number;
processing the plurality of information items, and extracting historical code submission information of the relevant code file relative to the first version number;
obtaining the name of the last submitter of the line number of the related code according to the historical code submission information;
sending the error record to the last submitter.
2. The method for managing code error records according to claim 1, wherein the obtaining an error record and recording a version number of a corresponding code resource generating the error record as a first version number, the error record is a software operation error caused by an error code, and then the obtaining a code trace based on the error record further comprises:
generating an ID number by using an MD5 algorithm according to the error record;
and searching whether the ID number exists in an ID library, if so, acquiring the name of a submitter corresponding to the ID number, and sending the error record to the submitter, otherwise, adding the ID number to the ID library.
3. The method for managing code error records according to claim 1, wherein the processing the plurality of information items to extract the historical code submission information of the relevant code file with respect to the first version number comprises:
and extracting the name of the related code file in the information item, and extracting historical code submission information of the related code file relative to the first version number by using a command in code submission version management software.
4. The method for managing code error records according to claim 1, wherein the obtaining the name of the last submitter of the relevant code line number according to the historical code submission information comprises:
obtaining all submission times of the relevant code line number according to the historical code submission information;
sequencing all submission times of the relevant code line numbers in the historical code submission information to obtain the final submission time;
and obtaining the name of the last submitter according to the last submission time.
5. The code error log management method of claim 1, wherein said sending the error log to the last submitter comprises:
sending the error record to the last submitter using mail.
6. A code error log management apparatus, comprising:
the device comprises an acquisition recording unit, a processing unit and a processing unit, wherein the acquisition recording unit is used for acquiring an error record and recording a corresponding code resource version number generating the error record as a first version number, and the error record is a software operation error caused by an error code;
the obtaining unit is used for obtaining a code trace based on the error record, wherein the code trace comprises the names of all relevant code files relevant to the error code and the line number of the relevant code;
the analysis unit is used for analyzing the code trace to obtain a plurality of information items, and each information item comprises the name of the related code file and a related code line number;
the processing unit is used for processing the plurality of information items and extracting historical code submission information of the related code file relative to the first version number;
the information integration unit is used for obtaining the name of the last submitter of the relevant code line number according to the historical code submission information;
a sending unit, configured to send the error record to the last submitter.
7. The code error log management device of claim 6, further comprising:
a generating unit, for generating an ID number by using MD5 algorithm according to the error record;
and the searching unit is used for searching whether the ID number exists in an ID library, if so, acquiring the name of a submitter corresponding to the ID number, sending the error record to the submitter, and if not, adding the ID number to the ID library.
8. The code error record management device according to claim 6, wherein the processing unit is specifically configured to;
and extracting the name of the related code file in the information item, and extracting historical code submission information of the related code file relative to the first version number by using a command in code submission version management software.
9. The code error record management device according to claim 6, wherein the information integrating unit includes:
the time acquisition unit is used for acquiring all submission times of the relevant code line number according to the historical code submission information;
the sequencing unit is used for sequencing all the submission times of the relevant code line numbers in the historical code submission information to obtain the final submission time;
and the name obtaining unit is used for obtaining the name of the last submitter according to the last submission time.
10. The code error record management device according to claim 6, wherein the sending unit is specifically configured to:
sending the error record to the last submitter by way of mail.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911414123.9A CN111240873A (en) | 2019-12-31 | 2019-12-31 | Code error record management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911414123.9A CN111240873A (en) | 2019-12-31 | 2019-12-31 | Code error record management method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111240873A true CN111240873A (en) | 2020-06-05 |
Family
ID=70863862
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911414123.9A Pending CN111240873A (en) | 2019-12-31 | 2019-12-31 | Code error record management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111240873A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106250319A (en) * | 2016-08-15 | 2016-12-21 | 腾讯科技（深圳）有限公司 | Static code scanning result treating method and apparatus |
| CN107168872A (en) * | 2017-05-11 | 2017-09-15 | 网易（杭州）网络有限公司 | Method, device, storage medium and the processor of code check |
| CN107729235A (en) * | 2017-09-29 | 2018-02-23 | 百度在线网络技术（北京）有限公司 | Method, apparatus, equipment and the computer-readable medium of the location code defect producer |
| WO2018169583A1 (en) * | 2017-03-16 | 2018-09-20 | Google Llc | Systems and methods for micro-scheduler testing framework |
| CN110188044A (en) * | 2019-05-30 | 2019-08-30 | 腾讯科技（深圳）有限公司 | Processing method, device, storage medium and the equipment of software error |
-
2019
- 2019-12-31 CN CN201911414123.9A patent/CN111240873A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106250319A (en) * | 2016-08-15 | 2016-12-21 | 腾讯科技（深圳）有限公司 | Static code scanning result treating method and apparatus |
| WO2018169583A1 (en) * | 2017-03-16 | 2018-09-20 | Google Llc | Systems and methods for micro-scheduler testing framework |
| CN107168872A (en) * | 2017-05-11 | 2017-09-15 | 网易（杭州）网络有限公司 | Method, device, storage medium and the processor of code check |
| CN107729235A (en) * | 2017-09-29 | 2018-02-23 | 百度在线网络技术（北京）有限公司 | Method, apparatus, equipment and the computer-readable medium of the location code defect producer |
| CN110188044A (en) * | 2019-05-30 | 2019-08-30 | 腾讯科技（深圳）有限公司 | Processing method, device, storage medium and the equipment of software error |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105573859A (en) | Data recovery method and device of database | |
| CN105512283A (en) | Data quality management and control method and device | |
| CN111240876B (en) | Fault positioning method and device for micro-service, storage medium and terminal | |
| CN109714249B (en) | Method and related device for pushing applet messages | |
| CN109284331B (en) | Certificate making information acquisition method based on service data resources, terminal equipment and medium | |
| CN105630656A (en) | Log model based system robustness analysis method and apparatus | |
| CN112328631A (en) | Production fault analysis method and device, electronic equipment and storage medium | |
| CN114385551B (en) | Log time-sharing management method, device, equipment and storage medium | |
| CN110245059B (en) | Data processing method, device and storage medium | |
| CN112256517B (en) | Log analysis method and device of virtualization platform based on LSTM-DSSM | |
| CN110019762B (en) | Problem positioning method, storage medium and server | |
| CN112068981B (en) | Knowledge base-based fault scanning recovery method and system in Linux operating system | |
| CN109542496B (en) | Method, device and system for determining incremental code | |
| US20110113006A1 (en) | Business process control apparatus, businesses process control method and business process control program | |
| CN111782264A (en) | Code classification information extraction method and device, computer equipment and storage medium | |
| CN111240873A (en) | Code error record management method and device | |
| CN116204540A (en) | Operation log recording method, device, equipment and storage medium | |
| CN112749197B (en) | Data fragment refreshing method, device, equipment and storage medium | |
| CN109246297B (en) | Method, device and storage medium for determining factory reset time of mobile terminal | |
| CN113760864A (en) | Data model generation method and device | |
| CN109491696B (en) | Method, device and system for determining incremental source code | |
| CN106775854B (en) | Method and device for generating configuration file | |
| CN112882721B (en) | Software package compiling method and device | |
| CN112699372A (en) | Vulnerability processing method and device and computer readable storage medium | |
| CN111311329B (en) | Tag data acquisition method, device, equipment and readable storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200605 |
|
| RJ01 | Rejection of invention patent application after publication |