CN112035161B - Applet release verification method and parallel release method - Google Patents
Applet release verification method and parallel release method Download PDFInfo
- Publication number
- CN112035161B CN112035161B CN202010899439.8A CN202010899439A CN112035161B CN 112035161 B CN112035161 B CN 112035161B CN 202010899439 A CN202010899439 A CN 202010899439A CN 112035161 B CN112035161 B CN 112035161B
- Authority
- CN
- China
- Prior art keywords
- applet
- release
- tasks
- variable
- parallel
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a method for verifying the release of an applet and a parallel release method, wherein the method for verifying the release of the applet comprises the following steps: setting a marking variable and setting an initial value for the marking variable; distributing a stack space for the running applet in the memory, and marking the marking variable of the applet in the memory; reading a tag variable; checking the value of the marking variable, and comparing the value with the initial value of the marking variable; and writing the content of the marked variable change in the comparison result into the memory, and completing the release of the applet. The method for parallel issuing of the applets comprises the step of respectively performing issuing verification on each individual applet by adopting the issuing verification method when at least 2 applets are issued in parallel. The invention can realize that the same applet is operated by a plurality of persons at the same time to issue, avoid the conditions of coverage and repeated operation, reduce the waiting time of issue and effectively improve the stability of the system.
Description
Technical Field
The invention relates to the technical field of Internet, in particular to a method for verifying applet release and a parallel release method.
Background
With the continuous development of internet technology, the scale of network application is continuously enlarged, the internet is gradually integrated into various fields of society, and along with the development of politics, economy, education, medical treatment, culture and other fields, the emerging mobile internet application scene is continuously emerging, and the development and optimization of an applet publishing platform are continuously promoted.
However, existing applet distribution platforms, while providing convenience for distribution, gradually expose the following drawbacks: 1. the developer can appear covering the condition when carrying out parallel operation: when a plurality of persons operate the same applet for distribution at the same time, the two programs are covered, and the cost for checking the problems is increased. 2. The release time is too long and unstable: the time required to wait from the release to the verification is too long, and release failure often exists, so that the efficiency is low and the experience is poor.
Therefore, designing an applet publishing method capable of realizing parallel applet publishing and verification, and having high efficiency, low cost and good experience is a technical problem to be solved.
Disclosure of Invention
Aiming at the problems in the prior art, the invention provides a method for issuing and checking the applet and a parallel issuing method, which can realize parallel issuing and checking of the applet, has high efficiency, low cost and good experience, and can improve the efficiency from development to issuing of the applet.
In order to achieve the above purpose, the technical scheme of the invention is as follows:
according to one aspect of the present invention, there is provided a method for applet distribution verification, comprising:
s101: setting a tag variable, including a build ID and a release state variable, and setting an initial value for the tag variable;
s102: distributing a stack space for the running applet in a memory, and marking a marking variable of the applet in the memory;
s103: reading the tag variable in step S102;
s104: checking the value of the marking variable read in the step S103, and comparing the value with the initial value of the marking variable;
s105: and (3) writing the content of the marked variable change into a memory in the comparison result in the step S104, and completing the release of the applet.
Preferably, the initial value of the build ID is "0", and the initial value of the distribution state of the applet is "false".
Preferably, when the applet distribution is completed, the published markup variables of the applet are cleaned.
Based on another aspect of the invention, a method for parallel issuing of applets is provided, wherein when at least 2 applets are issued in parallel, the issuing verification method is adopted to respectively carry out issuing verification on each individual applet.
Preferably, the parallel distribution of at least 2 applets comprises the following steps:
s201: issuing parallel execution tasks, and setting a mark variable, wherein the mark variable comprises a construction ID and an issuing state;
s202: the mark variable of the parallel execution task is received and recorded by a release server;
s203: the publishing server publishes the marked variable recorded by the publishing server and writes the marked variable into a database server, wherein the publishing state record is 'in publishing'; if the writing fails, executing step S201, and if the writing succeeds, executing step S204;
s204: reading information about the released dependent configuration items in the database server, executing step S201 if the reading fails, and executing step S205 if the reading succeeds;
s205: comparing, analyzing and assembling the dependent configuration item information to obtain configuration information which can be released;
s206: creating applet publishing tasks in batches, and counting and recording the number of applet publishing tasks of the batch tasks;
s207, performing batch parallel execution release on the applet release tasks created in the step S206, and counting and recording the number of the applet release tasks successfully executed;
s208: comparing the number of the applet publishing tasks recorded in the step S206 and the step S207, and modifying the publishing state in the database server to be 'successful' if the number is the same; and if the number is different, modifying the release state in the database server into release failure.
Preferably, when the release state is modified, the release state modification result prompt is performed.
Preferably, the dependent configuration item information includes, but is not limited to: base library version number, release package version, release history version, branches, size.
Preferably, the comparing in the step S205 includes the steps of:
s501: acquiring the lowest basic library version number supported by an applet publishing package to be published;
s502: searching a set of lowest base library version numbers which are larger than or equal to the lowest base library version numbers supported by the current release package from all base library version numbers;
s503: searching a version number with the number of the release records being empty from the set, and storing the record through an array;
s504: searching the largest release package version information under the version from the array, judging whether the version number of the basic library is smaller than 1, if so, continuing searching, and if so, ending searching;
s505: and returning valid configuration information which is available for release.
Preferably, in step S206, the counting and recording the number of the applet issuing tasks of the batch task includes:
finding executable applet issuing task data according to the configuration information for issuing, and inserting each piece of found applet issuing task data into a task array;
and carrying out batch creation of the applet issuing tasks on the task array through the Node service, and counting and recording the number of the applet issuing tasks of the batch tasks from the returned result set.
Preferably, the comparing in the step S208 includes:
reading the number of the applet issuing tasks of the batch task and the number of the applet issuing tasks successfully executed;
if the number of the applet issuing tasks which are successfully executed is smaller than the number of the applet issuing tasks of the batch tasks at the time, the parallel tasks are failed to be issued, otherwise, the parallel tasks are successfully issued.
The beneficial effects of the invention are as follows:
the application provides a method for verifying the release of the applet and a parallel release method, wherein the marking variable is set to read, verify, write, clean and the like, so that the real-time verification of the release state is realized, and the situations of coverage or repeated operation and the like of a developer in the release process are avoided. Meanwhile, when the system is issued in parallel, the execution state is recorded and checked, so that the issuing time is effectively reduced, the stability of the system is improved, and the time cost and the material cost in the issuing process are effectively reduced.
Drawings
In order to more clearly illustrate the embodiments of the invention or the solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art and are necessary are briefly described below, it being obvious that the drawings in the description below are only some embodiments of the invention and that other drawings can be obtained from them without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of a method for applet distribution verification according to an embodiment of the present invention;
fig. 2 is a flow chart of a method for parallel issuing of applets according to an embodiment of the invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
In some of the flows described in the specification and claims of the present invention and in the foregoing figures, a plurality of operations occurring in a particular order are included, but it should be understood that the operations may be performed out of order or performed in parallel, with the order of operations such as S1, S2, etc., being merely used to distinguish between the various operations, the order of the operations itself not representing any order of execution. In addition, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel.
The embodiment of the invention provides a method for issuing and checking an applet and a parallel issuing method, wherein the issuing execution state is recorded and checked by setting a mark variable, so that the parallel issuing and checking of the applet are realized, and the issuing efficiency of the applet is improved.
The method for verifying applet release and the method for parallel release, which are claimed in the present invention, will be described in detail in the following with reference to specific embodiments.
Referring to fig. 1, an embodiment of the present invention provides a method for verifying applet release, including:
s101: setting a tag variable, including a build ID and a release state variable, and setting an initial value for the tag variable;
s102: distributing a stack space for the running applet in a memory, and marking a marking variable of the applet in the memory;
s103: reading the tag variable in step S102;
s104: checking the value of the marking variable read in the step S103, and comparing the value with the initial value of the marking variable;
s105: and (3) writing the content of the marked variable change into a memory in the comparison result in the step S104, and completing the release of the applet.
Preferably, the initial value of the build ID is "0", and the initial value of the distribution state of the applet is "false".
Preferably, when the applet distribution is completed, the published markup variables of the applet are cleaned.
In specific implementation, the embodiment of the invention can realize the method by creating the mark reading function, the checking function, the writing function and the cleaning function; firstly, declaring a tag variable, wherein the content of the tag variable comprises a build ID with an initial value of 0 and a release state with a default value of false, and a stack space is allocated for the tag variable in a memory when a program runs; reading the mark variable of the memory space by adopting a mark reading function; checking the value of the tag variable read in step S103 using a tag check function, and comparing it with an initial value of the tag variable; and writing the content of the change of the mark variable into a memory by using a mark writing function in the comparison result, and completing the release of the applet. The tag cleaning function cleans the tag content that was disabled at the end of this release. Through the steps, the state of the applet can be checked before the applet is released, so that the situations of coverage and repeated operation of operators during operation are avoided.
Referring to fig. 2, an embodiment of the present invention provides a method for parallel issuing of applets, where when at least 2 applets are issued in parallel, the foregoing issue verification method is adopted to perform issue verification on each individual applet.
Preferably, the parallel distribution of at least 2 applets comprises the following steps:
s201: issuing parallel execution tasks, and setting a mark variable, wherein the mark variable comprises a construction ID and an issuing state;
s202: the mark variable of the parallel execution task is received and recorded by a release server;
s203: the publishing server publishes the marked variable recorded by the publishing server and writes the marked variable into a database server, wherein the publishing state record is 'in publishing'; if the writing fails, executing step S201, and if the writing succeeds, executing step S204;
s204: reading information about the released dependent configuration items in the database server, executing step S201 if the reading fails, and executing step S205 if the reading succeeds;
s205: comparing, analyzing and assembling the dependent configuration item information to obtain configuration information which can be released;
s206: creating applet publishing tasks in batches, and counting and recording the number of applet publishing tasks of the batch tasks; specifically, batch creation of release tasks can be performed according to different platforms and different areas, statistics can be performed in the execution function scope, and the number of the small program release tasks of the batch tasks can be counted.
S207, performing batch parallel execution release on the applet release tasks created in the step S206, and counting and recording the number of the applet release tasks successfully executed; specifically, the applet publishing tasks created in step S206 are synchronously executed and published in batches, the result condition of each publishing task is counted in the execution function scope, and the number of applet publishing tasks successfully executed is recorded.
S208: comparing the number of the applet publishing tasks recorded in the step S206 and the step S207, and modifying the publishing state in the database server to be 'successful' if the number is the same; and if the number is different, modifying the release state in the database server into release failure.
Preferably, when the release state is modified, the release state modification result prompt is performed.
Preferably, the dependent configuration item information includes, but is not limited to: base library version number, release package version, release history version, branches, size.
Preferably, the comparing in the step S205 includes the steps of:
s501: acquiring the lowest basic library version number supported by an applet publishing package to be published;
s502: searching a set of lowest base library version numbers which are larger than or equal to the lowest base library version numbers supported by the current release package from all base library version numbers; in particular, a cyclic traversal method may be employed in the search, for example: and carrying out circulating traversal on all the base library version numbers to find out a version number set which is larger than or equal to the minimum base library version supported by the current applet issuing package.
S503: searching a version number with the number of the release records being empty from the set, and storing the record through an array; specifically, the version number set data in step S502 is searched one by one for a version number with an empty release record number, and the record is stored after incremental sorting is performed by using an array.
S504: and searching the largest release package version information under the version from the array, judging whether the version number of the basic library is smaller than 1, if so, continuing searching, and if so, ending searching. Specifically, the array in step S503 is circularly traversed, the largest release packet version information under the version is recursively searched downward, whether the base library version number is smaller than 1 is judged, if not, the recursion search is continued, if yes, the search is ended, and the data object is returned.
S505: and returning valid configuration information which is available for release.
Preferably, in step S206, the counting and recording the number of the applet issuing tasks of the batch task includes:
finding executable applet issuing task data according to the configuration information for issuing, and inserting each piece of found applet issuing task data into a task array; specifically, according to the configuration information available for release, performing dual for loop nesting execution according to the client platform to be released and the region number, and simultaneously inserting each piece of generated applet release task data into a task array.
And carrying out batch creation of the applet issuing tasks on the task array through the Node service, and counting and recording the number of the applet issuing tasks of the batch tasks from the returned result set. Specifically, the task array is issued in batch by a static method all provided by a Promise object in Node service, circulation traversal is performed in a returned result set, and the total number of successful tasks is counted and recorded for subsequent verification.
Preferably, the comparing in the step S208 includes:
reading the number of the applet issuing tasks of the batch task and the number of the applet issuing tasks successfully executed;
if the number of the applet issuing tasks which are successfully executed is smaller than the number of the applet issuing tasks of the batch tasks at the time, the parallel tasks are failed to be issued, otherwise, the parallel tasks are successfully issued.
The method for issuing verification of the applet and the method for issuing the applet in parallel are simple in implementation, ensure that issuing of each version is effective in essence orderly, and avoid repeated operation and coverage of operators by setting the mark variable and performing operations such as reading, verification, writing and cleaning on the mark variable. Meanwhile, when the system is issued in parallel, the waiting time of the issuing is effectively reduced by recording, checking the execution state and the like, the stability of the system can be effectively improved, and the time cost and the money cost of the issuing are reduced.
The foregoing has shown and described the basic principles, principal features and advantages of the invention. It will be understood by those skilled in the art that the present invention is not limited to the embodiments described above, and that the above embodiments and descriptions are merely illustrative of the principles of the present invention, and various changes and modifications may be made without departing from the spirit and scope of the invention, which is defined in the appended claims. The scope of the invention is defined by the appended claims and equivalents thereof.
Claims (8)
1. A method of applet release verification, the method comprising:
s101: setting a mark variable, including a construction ID and a release state variable, and setting an initial value for the mark variable, wherein the initial value of the construction ID is 0, and the release state initial value of the applet is false;
s102: distributing a stack space for the running applet in a memory, and marking a marking variable of the applet in the memory;
s103: reading the tag variable in step S102;
s104: checking the value of the marking variable read in the step S103, and comparing the value with the initial value of the marking variable;
s105: writing the content of the change of the marker variable into a memory in the comparison result in the step S104, completing the release of the applet, cleaning the marker variable of the applet released when the release of the applet is completed, performing reading, checking, writing and cleaning operations on the marker variable by setting the marker variable, and checking the applet state before the release of the applet.
2. A method for parallel distribution of applets, characterized in that when at least 2 applets are distributed in parallel, the distribution verification method according to claim 1 is adopted to perform distribution verification on each individual applet.
3. A method of parallel publication of applets according to claim 2, wherein said parallel publication of at least 2 applets comprises the steps of:
s201: issuing parallel execution tasks, and setting a mark variable, wherein the mark variable comprises a construction ID and an issuing state;
s202: the mark variable of the parallel execution task is received and recorded by a release server;
s203: the publishing server publishes the marked variable recorded by the publishing server and writes the marked variable into a database server, wherein the publishing state record is 'in publishing'; if the writing fails, executing step S201, and if the writing succeeds, executing step S204;
s204: reading information about the released dependent configuration items in the database server, executing step S201 if the reading fails, and executing step S205 if the reading succeeds;
s205: comparing, analyzing and assembling the dependent configuration item information to obtain configuration information which can be released;
s206: creating applet publishing tasks in batches, and counting and recording the number of applet publishing tasks of the batch tasks;
s207, performing batch parallel execution release on the applet release tasks created in the step S206, and counting and recording the number of the applet release tasks successfully executed;
s208: comparing the number of the applet publishing tasks recorded in the step S206 and the step S207, and modifying the publishing state in the database server to be 'successful' if the number is the same; and if the number is different, modifying the release state in the database server into release failure.
4. A method for parallel distribution of applets according to claim 3, wherein the distribution state modification result prompt is performed when the distribution state modification is performed.
5. A method of applet parallel publication according to claim 3 wherein the dependent configuration item information comprises: base library version number, release package version, release history version, branches, size.
6. The method according to claim 5, wherein said comparing in said step S205 comprises the steps of:
s501: acquiring the lowest basic library version number supported by an applet publishing package to be published;
s502: searching a set of lowest base library version numbers which are larger than or equal to the lowest base library version numbers supported by the current release package from all base library version numbers;
s503: searching a version number with the number of the release records being empty from the set, and storing the record through an array;
s504: searching the largest basic library version number under the version number with the empty starting record number from the array, judging whether the basic library version number is smaller than 1, if so, continuing searching, and if so, ending searching;
s505: and returning valid configuration information which is available for release.
7. A method for parallel distribution of applets according to claim 3, wherein in step S206, the counting and recording the number of the applet distribution tasks of the batch task includes:
finding executable applet issuing task data according to the configuration information for issuing, and inserting each piece of found applet issuing task data into a task array;
and carrying out batch creation of the applet issuing tasks on the task array through the Node service, and counting and recording the number of the applet issuing tasks of the batch tasks from the returned result set.
8. A method of applet parallel distribution according to claim 3 wherein the comparison in step S208 comprises:
reading the number of the applet issuing tasks of the batch task and the number of the applet issuing tasks successfully executed;
if the number of the applet issuing tasks which are successfully executed is smaller than the number of the applet issuing tasks of the batch tasks at the time, the parallel tasks are failed to be issued, otherwise, the parallel tasks are successfully issued.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010899439.8A CN112035161B (en) | 2020-08-31 | 2020-08-31 | Applet release verification method and parallel release method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010899439.8A CN112035161B (en) | 2020-08-31 | 2020-08-31 | Applet release verification method and parallel release method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112035161A CN112035161A (en) | 2020-12-04 |
| CN112035161B true CN112035161B (en) | 2023-05-12 |
Family
ID=73587747
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010899439.8A Active CN112035161B (en) | 2020-08-31 | 2020-08-31 | Applet release verification method and parallel release method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112035161B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107015842A (en) * | 2017-03-31 | 2017-08-04 | 武汉票据交易中心有限公司 | A kind of management method and system of server compiling and issue |
| JP2018063520A (en) * | 2016-10-12 | 2018-04-19 | 株式会社日立製作所 | Computer system and program release management method |
| CN108196851A (en) * | 2017-12-28 | 2018-06-22 | 腾讯科技（深圳）有限公司 | Using dissemination method and device |
| CN109445837A (en) * | 2018-09-03 | 2019-03-08 | 中国平安人寿保险股份有限公司 | A kind of dissemination method and equipment of application program |
| CN109739529A (en) * | 2018-12-04 | 2019-05-10 | 贵阳朗玛信息技术股份有限公司 | A kind of method and device that program is issued automatically |
| CN111538525A (en) * | 2020-03-20 | 2020-08-14 | 成都药王科技股份有限公司 | Quick iteration and rollback method for program release |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8522207B1 (en) * | 2006-09-19 | 2013-08-27 | United Services Automobile Association (Usaa) | Systems and methods for automated centralized build/merge management |
| CN106775730A (en) * | 2016-12-21 | 2017-05-31 | 深圳Tcl数字技术有限公司 | Program dissemination method and system |
| CN109558162B (en) * | 2017-09-26 | 2021-08-10 | 腾讯科技（深圳）有限公司 | Application program issuing method and device, computer equipment and storage medium |
| CN109101267B (en) * | 2018-07-31 | 2021-11-23 | 上海携程金融信息服务有限公司 | Application release management method and device, electronic equipment and storage medium |
| CN110308917B (en) * | 2019-06-26 | 2024-02-23 | 深圳前海微众银行股份有限公司 | Applet issuing method, device, equipment and computer storage medium |
| CN110908698B (en) * | 2019-11-18 | 2023-09-19 | 上海新炬网络信息技术股份有限公司 | Automatic application program release method based on flow programming |
| CN111414172B (en) * | 2020-03-18 | 2023-03-31 | 时时同云科技(成都)有限责任公司 | Automatic deployment and release system and method for application software |
| CN111338684A (en) * | 2020-03-20 | 2020-06-26 | 成都药王科技股份有限公司 | Program publishing method |
| CN111367531B (en) * | 2020-03-26 | 2023-05-12 | 北京中指讯博数据信息技术有限公司 | Code processing method and device |
-
2020
- 2020-08-31 CN CN202010899439.8A patent/CN112035161B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2018063520A (en) * | 2016-10-12 | 2018-04-19 | 株式会社日立製作所 | Computer system and program release management method |
| CN107015842A (en) * | 2017-03-31 | 2017-08-04 | 武汉票据交易中心有限公司 | A kind of management method and system of server compiling and issue |
| CN108196851A (en) * | 2017-12-28 | 2018-06-22 | 腾讯科技（深圳）有限公司 | Using dissemination method and device |
| CN109445837A (en) * | 2018-09-03 | 2019-03-08 | 中国平安人寿保险股份有限公司 | A kind of dissemination method and equipment of application program |
| CN109739529A (en) * | 2018-12-04 | 2019-05-10 | 贵阳朗玛信息技术股份有限公司 | A kind of method and device that program is issued automatically |
| CN111538525A (en) * | 2020-03-20 | 2020-08-14 | 成都药王科技股份有限公司 | Quick iteration and rollback method for program release |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112035161A (en) | 2020-12-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112559554B (en) | Query statement optimization method and device | |
| CN110944048B (en) | Service logic configuration method and device | |
| CN1035193A (en) | Utilize index tree data-base recording to be carried out the method for concurrent access | |
| CN113778890B (en) | Code testing method and device, electronic equipment and storage medium | |
| CN109189343B (en) | Metadata disk-dropping method, device, equipment and computer-readable storage medium | |
| US10503823B2 (en) | Method and apparatus providing contextual suggestion in planning spreadsheet | |
| CN112035161B (en) | Applet release verification method and parallel release method | |
| US11080334B1 (en) | Graph representation system and methods | |
| CN112860581A (en) | Test case execution method, device, equipment and storage medium | |
| CN114676126B (en) | Database-based data verification method, device, equipment and storage medium | |
| CN113704519B (en) | Data set determining method and device, computer equipment and storage medium | |
| CN115437640A (en) | Method for quickly compiling engineering code | |
| CN113326046B (en) | Method and device for acquiring compiling time length | |
| CN110221952B (en) | Service data processing method and device and service data processing system | |
| CN113987107A (en) | Dialogue method and device based on behavior tree, electronic equipment and storage medium | |
| CN113742263A (en) | Bandwidth distribution determination and program optimization methods, devices and equipment | |
| CN114328171A (en) | Method, device and equipment for generating test case library and storage medium | |
| CN113391812A (en) | Analysis method and device of application program module and analysis tool | |
| CN113721916B (en) | Compiling method, device and equipment of operating system and readable storage medium | |
| CN114546884B (en) | Block chain batch transaction conflict detection method and system | |
| CN116340270B (en) | Concurrent traversal enumeration method, device, equipment and storage medium | |
| CN114816425B (en) | Method and system for converting an automation language program into a LUA language program | |
| CN110221971B (en) | Search engine testing method and device, electronic equipment and storage medium | |
| CN112860310A (en) | Tag-based data type identifier configuration method | |
| CN113590892A (en) | Transaction flow monitoring method and device, electronic equipment and 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |