CN113835731A - Method and device for prompting error according to updated component, electronic equipment and storage medium - Google Patents
Method and device for prompting error according to updated component, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113835731A CN113835731A CN202111140693.0A CN202111140693A CN113835731A CN 113835731 A CN113835731 A CN 113835731A CN 202111140693 A CN202111140693 A CN 202111140693A CN 113835731 A CN113835731 A CN 113835731A
- Authority
- CN
- China
- Prior art keywords
- component
- module
- target
- information
- updated
- 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
- 238000000034 method Methods 0.000 title claims abstract description 43
- 230000006870 function Effects 0.000 claims description 93
- 238000004590 computer program Methods 0.000 claims description 8
- 238000012217 deletion Methods 0.000 claims description 6
- 230000037430 deletion Effects 0.000 claims description 6
- 238000011161 development Methods 0.000 abstract description 16
- 230000000694 effects Effects 0.000 abstract description 7
- 238000007726 management method Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 9
- 238000007781 pre-processing Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 238000001514 detection method Methods 0.000 description 4
- 238000006243 chemical reaction Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000003909 pattern recognition Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013136 deep learning model Methods 0.000 description 1
- 238000010252 digital analysis Methods 0.000 description 1
- 239000012634 fragment Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- 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
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)
- Stored Programmes (AREA)
Abstract
The application provides a method and a device for prompting error according to an updated component, electronic equipment and a storage medium, and relates to the technical field of development management. The method comprises the following steps: the server receives the uploaded updating component; the updating component comprises component information, and the component information comprises a module identifier for describing a functional module with changed data in the updating component; determining a target component from the client based on the module identification, and determining a target function module from a plurality of function modules of the target component; replacing the target function module by using the function module with changed data to obtain an updated target assembly; and prompting error information to the client according to the updated target component. According to the method, the server is introduced to store, update, compare and detect the component information of the updated component, and error prompt is performed when the client uses the component of the old version, so that the problem that the compiling effect is poor or errors occur in the problem that the component version is not corresponding or not updated is solved.
Description
Technical Field
The application relates to the technical field of development management, in particular to a method and a device for prompting error according to an updated component, electronic equipment and a storage medium.
Background
When program development is performed in an integrated development environment, a development end generally uploads components to a server, and the server stores the components uploaded by all the development ends, so that each development end directly obtains required components from the server.
In the prior art, all local components are generally managed by using a local management tool, and component downloading is performed by using a project building system to connect the management tool, so that unified management of the components is realized. However, because of the numerous versions of the components, the development tool is only used for compiling at a code level when compiling, if compiling is failed directly due to a compiling error, and a user cannot know version update information when the components of the new version are uploaded.
Therefore, the development end or the server cannot perform machine detection on whether the version of the component is the latest version, and only the development personnel of the development end can search whether the component to be used has an updated version in the server warehouse when the development personnel have update consciousness or will, so that the method has overlarge workload and extremely low efficiency, the development personnel cannot perform traversal query on the version updates of all the components used when using the components every time, the version of the component is not updated timely, the development end still adopts the old version component which is locally used before when using the component, and the problem of poor compiling effect or error may occur due to the problem of the version of the component being not corresponding or not updated in the process.
Disclosure of Invention
In view of the above, an object of the embodiments of the present application is to provide a method, an apparatus, an electronic device, and a storage medium for prompting an error according to an updated component, so as to solve the problem in the prior art that an operation effect is poor or an error occurs due to a version of a component being not corresponding or updated in time.
The embodiment of the application provides an error prompting method according to an updated component, which comprises the following steps: the server receives the uploaded updating component; the updating component comprises component information, and the component information comprises a module identifier for describing a functional module with changed data in the updating component; determining a target component from a client based on the module identification, and determining a target function module from a plurality of function modules of the target component; replacing the target function module with the function module with changed data to obtain an updated target assembly; and prompting error information to the client according to the updated target component.
In the implementation mode, the server determines the updated function module according to the module identifier in the module information after receiving the uploaded update module, updates the target module when the target module of the client needs to use the updated function module, improves the update accuracy of the module, reduces the update workload, and meanwhile, gives an error prompt to the client when the client uses the module of a lower version before update, thereby avoiding poor compiling effect or errors caused by the problem that the version of the module is not corresponding or not updated when the client uses the module of a lower version before update.
Optionally, the determining a target function module from among the plurality of function modules of the target component includes: and comparing the names of the functional modules corresponding to the module identifiers in the updating assembly with the names of each functional module in the target assembly one by one, and taking the functional modules with the same names in the target assembly as the target functional modules.
In the implementation mode, the target function module in the target assembly is determined through name comparison of the function module, so that the assembly needing to use the function module is ensured to be screened out, updating or error prompt of the assembly without using the function module is avoided, and invalid processing is reduced.
Optionally, the prompting, according to the updated target component, the error information to the client includes: and when the version information of the pre-stored component stored in the client preset database is lower than the version information of the target component, prompting error information of inconsistent component versions to the client.
In the implementation mode, the version information of the pre-stored component stored in the client preset database is used as local comparison information and is compared with the version information of the target component, so that whether the version of the component needs to be updated or not is accurately judged.
Optionally, the determining a target component from the client based on the module identifier includes: and taking the component identification in the client side and the component identification of the updated component as the target component, wherein the component comprises the functional module corresponding to the module identification.
In the implementation mode, the target component is accurately determined from the client through the consistency comparison of the module identification and whether the component comprises the corresponding functional module, and the subsequent update and error prompt of the target component can be carried out.
Optionally, when the component information includes a newly added function module, adding the newly added function module to the target component.
Optionally, when the component information includes deletion information for deleting a function module, the corresponding function module is deleted from the target component according to the deletion information.
In the implementation mode, the target component is added and deleted with the function modules according to the component information, the component can be updated from the dimension of the function modules, and the occupation of the whole update of the conventional component on resources is reduced.
The embodiment of the application provides a device of making mistakes according to update subassembly suggestion, the device includes: the component information receiving module is used for receiving the uploaded updating component through the server; the updating component comprises component information, and the component information comprises a module identifier for describing a functional module with changed data in the updating component; the target component determining module is used for determining a target component from the client based on the module identifier and determining a target function module from a plurality of function modules of the target component; the updating module is used for replacing the target function module by using the function module with changed data to obtain an updated target assembly; and the prompting module is used for prompting error information to the client according to the updated target component.
In the implementation mode, the server determines the updated function module according to the module identifier in the module information after receiving the uploaded update module, updates the target module when the target module of the client needs to use the updated function module, improves the update accuracy of the module, reduces the update workload, and meanwhile, gives an error prompt to the client when the client uses the module of a lower version before update, thereby avoiding poor compiling effect or errors caused by the problem that the version of the module is not corresponding or not updated when the client uses the module of a lower version before update.
Optionally, the target component determination module is specifically configured to: and comparing the names of the functional modules corresponding to the module identifiers in the updating assembly with the names of each functional module in the target assembly one by one, and taking the functional modules with the same names in the target assembly as the target functional modules.
In the implementation mode, the target function module in the target assembly is determined through name comparison of the function module, so that the assembly needing to use the function module is ensured to be screened out, updating or error prompt of the assembly without using the function module is avoided, and invalid processing is reduced.
Optionally, the prompt module is specifically configured to: and when the version information of the pre-stored component stored in the client preset database is lower than the version information of the target component, prompting error information of inconsistent component versions to the client.
In the implementation mode, the version information of the pre-stored component stored in the client preset database is used as local comparison information and is compared with the version information of the target component, so that whether the version of the component needs to be updated or not is accurately judged.
Optionally, the target component determination module is specifically configured to: and taking the component identification in the client side and the component identification of the updated component as the target component, wherein the component comprises the functional module corresponding to the module identification.
In the implementation mode, the target component is accurately determined from the client through the consistency comparison of the module identification and whether the component comprises the corresponding functional module, and the subsequent update and error prompt of the target component can be carried out.
Optionally, the device for prompting an error according to an update component further includes: and the adding module is used for adding the adding function module into the target component when the component information comprises the adding function module.
Optionally, the device for prompting an error according to an update component further includes: and the deleting module is used for deleting the corresponding functional module from the target assembly according to the deleting information when the assembly information comprises the deleting information of the deleting functional module.
In the implementation mode, the target component is added and deleted with the function modules according to the component information, the component can be updated from the dimension of the function modules, and the occupation of the whole update of the conventional component on resources is reduced.
An embodiment of the present application further provides an electronic device, where the electronic device includes a memory and a processor, where the memory stores program instructions, and the processor executes steps in any one of the above implementation manners when reading and executing the program instructions.
The embodiment of the present application further provides a readable storage medium, in which computer program instructions are stored, and the computer program instructions are read by a processor and executed to perform the steps in any of the above implementation manners.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a schematic block diagram of a system for prompting an error according to an update component according to an embodiment of the present application.
Fig. 2 is a flowchart illustrating a method for prompting an error according to an update component according to an embodiment of the present disclosure.
Fig. 3 is a flowchart illustrating a step of updating version information of a pre-stored component according to an embodiment of the present application.
Fig. 4 is a block diagram of an error prompt apparatus according to an update component according to an embodiment of the present disclosure.
Icon: 11-a client; 12-a detection server; 13-a server repository; 30-prompting the error device according to the updated component; 31-a component information receiving module; 32-a target component determination module; 33-an update module; 34-prompt module.
Detailed Description
The technical solution in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
The applicant has found that the current management mode of the component is generally as follows: and managing all local components by using a management tool of the components, downloading the components by using the management tool of the package management platform connection component, and realizing a unified management mechanism aiming at the components. However, because the versions of components uploaded to the server of the management tool by different developers are numerous, the development tool is usually compiled only for code level compilation, for example, whether a referenced API (Application Programming Interface) exists or not, and if an error is found, the compilation is directly failed. There is no checking against the version in this process, resulting in that although the compilation is successful, it does not run as expected, and there may be a problem in that the functionality or efficiency of the component is relatively poor due to the version lag. There is also a case where the version number is artificially modified, and although compilation is not erroneous, there is also a problem that the functionality or efficiency of a component after running is relatively poor due to the version lag.
In order to solve the above problem, an embodiment of the present application provides a method for prompting an error according to an update component, where the method for prompting an error according to an update component is described first, and the method for prompting an error according to an update component in this embodiment may be implemented by a system for prompting an error according to an update component. Referring to fig. 1, fig. 1 is a schematic block diagram of an error notification system according to an update component according to an embodiment of the present application, where the error notification system according to an update component includes a client 11, a detection server 12, and a server warehouse 13, which are in communication connection with each other.
Next, a method for prompting an error according to an update component is described, please refer to fig. 2, and fig. 2 is a schematic flow chart of the method for prompting an error according to an update component according to an embodiment of the present application. The method for prompting the error according to the updated component can comprise the following specific steps:
step S21: the server receives the uploaded updated component.
In this embodiment, the server repository may be a Maven local repository, and when Nexus is used as the repository manager, the Maven local repository may perform component synchronization with the Maven central repository, and maintain the Maven local repository while acting on the remote repository.
The Maven is an open source Project developed by pure Java under Apache, and can manage steps of construction, report, document and the like of a Project by using a central information fragment based on a Project Object Model (POM) concept, so that the Maven is a Project management tool and can construct and manage Java projects dependently.
The Nexus is called Sonatiype Nexus, is a special remote warehouse, and is a warehouse service built in a local area network. When Maven needs to download a component, it requests from Nexus, if Nexus queries that the component is not present on Maven's local repository, it downloads from an external remote repository, i.e. Maven's central repository, caches on Maven's local repository and then services Maven's download.
Alternatively, the component in this embodiment may be a jar package commonly used in Java development, which is a self-contained Java application program, and may be directly executed by a jvm (Java Virtual machine) without previously fetching a file or setting a class path.
Optionally, the update component may further include component information in addition to the component package, where the component information includes a module identifier for describing a functional module in the update component, where data of the functional module is changed. For example, the component a for image processing includes function modules such as an image acquisition function module a1, an image preprocessing function module a2, and a deep learning model call function module A3, and after the client updates only the image preprocessing function module a2 of the component a, the component information includes a module identifier of the image preprocessing function module a 2.
Optionally, the component information in this embodiment may be combination information of a component name, a version number, uploading party information, a component identifier, and/or a module identifier expressed in a form of a hash code.
For example, if the component name of the image Recognition component is Pattern Recognition, the version number of the image Recognition component is 1.0.1, the uploading party information is a, the component identifier is B, and the module identifier is C, hash code conversion is performed on the combined information of the Pattern Recognition, 1.0.1, A, B, and C, and the obtained hash code is the component information corresponding to the component.
Besides the single uploader, the uploader information may be a collection of uploaders that have used the component, such as a/B/C/D. Optionally, the uploading party information a in this embodiment may be any identification information of the uploading party, such as a Media Access Control Address (MAC Address), a Maven account, and the like.
When the uploader information is the client set of the uploader who has used the component, each uploader may add its own identification information to the existing uploader information when the component is uploaded, and then perform hash conversion of the component information.
Step S22: and determining the target component from the client based on the module identification, and determining the target function module from a plurality of function modules of the target component.
There may be one or more components that the client locally stores or uses, and thus it is necessary to determine whether there is a target component corresponding to the updated component and a target function module among all components of the client.
Specifically, the manner of determining the target component may be: and taking the component identification in the client side and the component identification of the updated component as the target component, wherein the component comprises the functional module corresponding to the module identification.
For example, the function module that has changed in the updated component is the image preprocessing function module a2, the component with the consistent component identifier is queried in the client according to the component identifier of the updated component, and then it is determined that the component includes the function module a2 that has changed in function, and the component in the client is taken as the target component. Then, the names of the function modules corresponding to the module identifiers of the image preprocessing function module a2 are compared with the names of each function module in the target assembly one by one, and the function modules with the same names in the target assembly are used as target function modules.
Optionally, in this embodiment, before comparing the module identifier and the component identifier of the component information, component information corresponding to the target component needs to be acquired in the server repository, and in this embodiment, the query may be performed in the server repository based on the component name and by using a tree structure.
Optionally, in addition to the component name, the component name may be a character that can be queried in the server repository according to an address of the component or other characters. For example, when an address is adopted for query, the corresponding tree structure is a tree structure address, and the corresponding node in the server warehouse can obtain the component information corresponding to the component through the address; or when the component name is adopted for query, the component name corresponds to the component information one by one, and the nodes with the node attributes containing the component name are traversed in the tree structure to obtain the corresponding component information.
It should be understood that all the steps of step S22 in this embodiment may be performed by the detection server, which performs the functions of data query, determination, etc. of the target component, target function module, etc. through interaction with the client and the server repository.
Step S23: and replacing the target function module by using the function module with changed data to obtain the updated target assembly.
Alternatively, in step S23, the server may replace the target function module of the client with the function module with changed data, or the client may replace the target function module with the function module with changed data, so as to obtain the updated target component.
Further, in this embodiment, the function module may be added or deleted from the target component, for example, when the component information includes a newly added function module, the newly added function module is added to the target component, or when the component information includes deletion information of a deleted function module, the corresponding function module is deleted from the target component according to the deletion information.
Step S24: and prompting error information to the client according to the updated target component.
The component information includes a version number used for representing a component currently used by the client, but after the component currently used by the client is downloaded to the local, a component with an updated version may be stored in the server repository.
Specifically, when the version information of the pre-stored component stored in the client preset database is lower than the version information of the target component, error information indicating that the versions of the components are inconsistent is prompted to the client.
Generally, the larger the numerical value of the version number is, the newer the version is, for example, the version number of the component a is 1.01, the version number of the component B is 1.02, the component B is newer than the version of the component a, when the version number in the version information of the target component is smaller than the version number of the version information of the prestored component stored in the preset database of the client, the target component is an updated version, and the version of the component used by the client is an older version, the client is subjected to component inconsistency error reporting and/or is prohibited from using the component, so that the client is ensured to avoid using the component of the older version, and is prompted to update the component, thereby solving the problem that the running effect is poor or an error occurs due to the fact that the component version is not corresponding or updated in time.
Optionally, after obtaining the component information corresponding to the target component, a specific comparison manner may be to convert the updated component information of the target component and the pre-stored component information from the hash code into a component name, a version number, upload party information, a module identifier, a component identifier, and the like, and compare version numbers of the component information and the pre-stored component information.
Optionally, the hash code conversion in this embodiment may be implemented based on a hash algorithm such as a direct addressing method, a digital analysis method, a folding method, and the like, and in order to restore the hash code to the component information, the corresponding relationship between the hash code and the character in the hash algorithm may be stored, and the hash code is restored based on the corresponding relationship when the hash code is restored.
For the version information of the pre-stored component stored in the client preset database, the version information may be stored along with the component information, and when the version information of the pre-stored component is stored, update timeliness may be ensured through a parallel mechanism of first storing and updating, please refer to fig. 3, where fig. 3 is a schematic flow diagram of a step of updating the version information of the pre-stored component provided in an embodiment of the present application, and specific steps may be as follows:
step S251: and when the component information corresponding to the target component is stored as the pre-stored component information, judging whether the pre-stored component information exists locally at the client.
Since the client may download the package for the first time or download the component in the previous compiling development, and the client has the pre-stored component information downloaded before, the present embodiment needs to determine whether the pre-stored component information is already stored locally at the client when storing the pre-stored component information, so as to execute the subsequent different actions.
Step S252: and when the pre-stored component information does not exist locally at the client, storing the component information corresponding to the component as the pre-stored component information.
Step S253: and when the pre-stored component information exists locally at the client, replacing the pre-stored component with the component information corresponding to the component.
In the steps, the condition that the pre-stored component information exists locally and the condition that the pre-stored component information does not exist are distinguished, so that the local pre-stored component information is stored or replaced and updated for the first time, and the updating timeliness of the pre-stored component information can be further realized.
In order to cooperate with the method for prompting an error according to an update component provided in the embodiment of the present application, an apparatus 30 for prompting an error according to an update component is further provided in the embodiment of the present application, please refer to fig. 4, and fig. 4 is a schematic block diagram of the apparatus for prompting an error according to an update component provided in the embodiment of the present application.
A component information receiving module 31, configured to receive the uploaded updated component through the server; the updating component comprises component information, and the component information comprises a module identifier for describing a functional module with changed data in the updating component;
a target component determination module 32, configured to determine a target component from the client based on the module identifier, and determine a target function module from a plurality of function modules of the target component;
an update module 33, configured to replace the target function module with the changed data, so as to obtain an updated target component;
and the prompting module 34 is used for prompting the client with error information according to the updated target component.
Optionally, the target component determining module 32 is specifically configured to: and comparing the names of the functional modules corresponding to the module identifiers in the updating assembly with the names of each functional module in the target assembly one by one, and taking the functional modules with the same names in the target assembly as the target functional modules.
Optionally, the prompt module 34 is specifically configured to: and when the version information of the pre-stored component stored in the client preset database is lower than the version information of the target component, prompting error information of inconsistent component versions to the client.
Optionally, the target component determining module 32 is specifically configured to: and taking the component identification in the client side and the component identification of the updated component as the target component, wherein the component comprises the functional module corresponding to the module identification.
Optionally, the device for prompting an error 30 according to the updated component further includes: and the adding module is used for adding the adding function module into the target component when the component information comprises the adding function module.
Optionally, the device for prompting an error 30 according to the updated component further includes: and the deleting module is used for deleting the corresponding functional module from the target assembly according to the deleting information when the assembly information comprises the deleting information of the deleting functional module.
The embodiment of the application further provides electronic equipment, which comprises a memory and a processor, wherein program instructions are stored in the memory, and when the processor reads and runs the program instructions, the steps in any one of the methods for prompting the error according to the update component provided by the embodiment are executed.
It should be understood that the electronic device may be a Personal Computer (PC), a tablet PC, a smart phone, a Personal Digital Assistant (PDA), or other electronic device having a logical computing function.
The embodiment of the application also provides a readable storage medium, wherein computer program instructions are stored in the readable storage medium, and when the computer program instructions are read and operated by a processor, the steps in the method for prompting the error according to the updating component are executed.
To sum up, the embodiment of the present application provides a method, an apparatus, an electronic device, and a storage medium for prompting an error according to an update component, where the method includes: the server receives the uploaded updating component; the updating component comprises component information, and the component information comprises a module identifier for describing a functional module with changed data in the updating component; determining a target component from a client based on the module identification, and determining a target function module from a plurality of function modules of the target component; replacing the target function module with the function module with changed data to obtain an updated target assembly; and prompting error information to the client according to the updated target component.
In the implementation mode, the server determines the updated function module according to the module identifier in the module information after receiving the uploaded update module, updates the target module when the target module of the client needs to use the updated function module, improves the update accuracy of the module, reduces the update workload, and meanwhile, gives an error prompt to the client when the client uses the module of a lower version before update, thereby avoiding poor compiling effect or errors caused by the problem that the version of the module is not corresponding or not updated when the client uses the module of a lower version before update.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. The apparatus embodiments described above are merely illustrative, and for example, the block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of devices according to various embodiments of the present application. In this regard, each block in the block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams, and combinations of blocks in the block diagrams, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Therefore, the present embodiment further provides a readable storage medium, in which computer program instructions are stored, and when the computer program instructions are read and executed by a processor, the computer program instructions perform the steps of any of the block data storage methods. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including 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 description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (9)
1. A method for prompting an error based on an updated component, the method comprising:
the server receives the uploaded updating component; the updating component comprises component information, and the component information comprises a module identifier for describing a functional module with changed data in the updating component;
determining a target component from a client based on the module identification, and determining a target function module from a plurality of function modules of the target component;
replacing the target function module with the function module with changed data to obtain an updated target assembly;
and prompting error information to the client according to the updated target component.
2. The method of claim 1, wherein determining a target function module from the plurality of function modules of the target component comprises:
and comparing the names of the functional modules corresponding to the module identifiers in the updating assembly with the names of each functional module in the target assembly one by one, and taking the functional modules with the same names in the target assembly as the target functional modules.
3. The method of claim 1, wherein the prompting the client for error information based on the updated target component comprises:
and when the version information of the pre-stored component stored in the client preset database is lower than the version information of the target component, prompting error information of inconsistent component versions to the client.
4. The method of claim 1, wherein determining the target component from the client based on the module identifier comprises:
and taking the component identification in the client side and the component identification of the updated component as the target component, wherein the component comprises the functional module corresponding to the module identification.
5. The method of claim 1, wherein when the component information includes a newly added function module, adding the newly added function module to the target component.
6. The method according to claim 1, wherein when the component information includes deletion information for deleting a function module, the corresponding function module is deleted from the target component according to the deletion information.
7. An apparatus for prompting an error based on an updated component, the apparatus comprising:
the component information receiving module is used for receiving the uploaded updating component through the server; the updating component comprises component information, and the component information comprises a module identifier for describing a functional module with changed data in the updating component;
the target component determining module is used for determining a target component from the client based on the module identifier and determining a target function module from a plurality of function modules of the target component;
the updating module is used for replacing the target function module by using the function module with changed data to obtain an updated target assembly;
and the prompting module is used for prompting error information to the client according to the updated target component.
8. An electronic device comprising a memory having stored therein program instructions and a processor that, when executed, performs the steps of the method of any of claims 1-6.
9. A storage medium having stored thereon computer program instructions for executing the steps of the method according to any one of claims 1 to 6 when executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111140693.0A CN113835731A (en) | 2021-09-28 | 2021-09-28 | Method and device for prompting error according to updated component, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111140693.0A CN113835731A (en) | 2021-09-28 | 2021-09-28 | Method and device for prompting error according to updated component, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113835731A true CN113835731A (en) | 2021-12-24 |
Family
ID=78970801
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111140693.0A Pending CN113835731A (en) | 2021-09-28 | 2021-09-28 | Method and device for prompting error according to updated component, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113835731A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114647854A (en) * | 2022-03-01 | 2022-06-21 | 深圳开源互联网安全技术有限公司 | Component security detection method and device, firewall and component downloading system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104965721A (en) * | 2014-07-10 | 2015-10-07 | 腾讯科技（深圳）有限公司 | Method and apparatus for updating an application |
| CN106227541A (en) * | 2016-07-27 | 2016-12-14 | 乐视控股（北京）有限公司 | A kind of program updates download process method and mobile terminal |
| CN108108181A (en) * | 2017-12-14 | 2018-06-01 | 深圳市雷鸟信息科技有限公司 | The function renewal method, apparatus and computer readable storage medium of application program |
| CN108287726A (en) * | 2017-03-03 | 2018-07-17 | 广州市动景计算机科技有限公司 | Update detection method, device and the service terminal of extension |
| WO2019029457A1 (en) * | 2017-08-07 | 2019-02-14 | 阿里巴巴集团控股有限公司 | Method and apparatus for updating application program on client, and electronic device |
| CN109656595A (en) * | 2018-12-10 | 2019-04-19 | 北京百家互联科技有限公司 | The method, apparatus and system that client-side program updates |
| CN111736876A (en) * | 2020-06-28 | 2020-10-02 | 北京云族佳科技有限公司 | Client update control method, device, storage medium and server |
| CN113254045A (en) * | 2021-06-07 | 2021-08-13 | 中电金信软件有限公司 | Software initialization method, system and computer readable storage medium |
-
2021
- 2021-09-28 CN CN202111140693.0A patent/CN113835731A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104965721A (en) * | 2014-07-10 | 2015-10-07 | 腾讯科技（深圳）有限公司 | Method and apparatus for updating an application |
| CN106227541A (en) * | 2016-07-27 | 2016-12-14 | 乐视控股（北京）有限公司 | A kind of program updates download process method and mobile terminal |
| CN108287726A (en) * | 2017-03-03 | 2018-07-17 | 广州市动景计算机科技有限公司 | Update detection method, device and the service terminal of extension |
| WO2019029457A1 (en) * | 2017-08-07 | 2019-02-14 | 阿里巴巴集团控股有限公司 | Method and apparatus for updating application program on client, and electronic device |
| CN108108181A (en) * | 2017-12-14 | 2018-06-01 | 深圳市雷鸟信息科技有限公司 | The function renewal method, apparatus and computer readable storage medium of application program |
| CN109656595A (en) * | 2018-12-10 | 2019-04-19 | 北京百家互联科技有限公司 | The method, apparatus and system that client-side program updates |
| CN111736876A (en) * | 2020-06-28 | 2020-10-02 | 北京云族佳科技有限公司 | Client update control method, device, storage medium and server |
| CN113254045A (en) * | 2021-06-07 | 2021-08-13 | 中电金信软件有限公司 | Software initialization method, system and computer readable storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114647854A (en) * | 2022-03-01 | 2022-06-21 | 深圳开源互联网安全技术有限公司 | Component security detection method and device, firewall and component downloading system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8032880B2 (en) | Multi-branch management for updating software | |
| US7243346B1 (en) | Customized library management system | |
| US10621211B2 (en) | Language tag management on international data storage | |
| US8108360B2 (en) | Database object update order determination | |
| EP3014479A2 (en) | Omega names: name generation and derivation | |
| CN111258614B (en) | Method, system, equipment and storage medium for detecting upgrade exception of project third-party library | |
| CN114510267B (en) | Program ABI interface compatibility calculation method based on Linux system | |
| CN104679500B (en) | Method and device for realizing automatic generation of entity class | |
| CN113420026B (en) | Database table structure changing method, device, equipment and storage medium | |
| CN111736762B (en) | Synchronous updating method, device, equipment and storage medium of data storage network | |
| CN113515303B (en) | Project transformation method, device and equipment | |
| US10606805B2 (en) | Object-level image query and retrieval | |
| CN113835731A (en) | Method and device for prompting error according to updated component, electronic equipment and storage medium | |
| CN114461217A (en) | Code compiling method and device, electronic equipment and storage medium | |
| CN112988220A (en) | Application configuration updating method and device, storage medium and server | |
| CN111984264A (en) | Static library generation method and device | |
| CN109032641B (en) | Application version updating method and device | |
| CN115729590A (en) | Service deployment method, device, equipment and computer readable storage medium | |
| CN115543429A (en) | Project environment building method, electronic equipment and computer readable storage medium | |
| US7389515B1 (en) | Application deflation system and method | |
| CN114816470A (en) | Metadata database management method and device, electronic equipment and medium | |
| CN115964061A (en) | Plug-in updating method and device, electronic equipment and computer readable storage medium | |
| CN114089962A (en) | Component management method, device and medium | |
| US11256602B2 (en) | Source code file retrieval | |
| CN116302206B (en) | Presto data source hot loading method based on MQ |
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 |