CN116048590A - Production line problem repairing method, device, electronic equipment and computer readable medium - Google Patents
Production line problem repairing method, device, electronic equipment and computer readable medium Download PDFInfo
- Publication number
- CN116048590A CN116048590A CN202310158466.3A CN202310158466A CN116048590A CN 116048590 A CN116048590 A CN 116048590A CN 202310158466 A CN202310158466 A CN 202310158466A CN 116048590 A CN116048590 A CN 116048590A
- Authority
- CN
- China
- Prior art keywords
- user
- code
- target machine
- information
- production line
- 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
- 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
-
- 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
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
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)
Abstract
Embodiments of the present disclosure disclose a production line problem repair method, apparatus, electronic device, and computer readable medium. One embodiment of the method comprises the following steps: acquiring identification information of a user in response to detection of login operation of the user; judging whether the user is a white list user or not based on the identification information; assigning the user to a target machine and executing code on the target machine in response to the user being a whitelisted user, wherein the whitelisted user includes problem feedback information for the user; and modifying the byte code of the code on the target machine based on the hot update code, and repairing the production line problem corresponding to the problem feedback information on the target machine. The implementation method realizes the technology of updating with code heat, can quickly solve the production line problem under the condition of not going through the version release flow, and can not influence the use of other normal users.
Description
Technical Field
Embodiments of the present disclosure relate to the field of computer technology, and in particular, to a method, an apparatus, an electronic device, and a computer readable medium for repairing a production line problem.
Background
After a production line problem occurs in an item, a method for checking the problem usually reaches the condition that the test environment is repeated, but if the condition that the test environment cannot be repeated or the reproduction is time-consuming is encountered, the problem needs to be checked in the production line, and aiming at the problem which is not easy to check, the problem needs to be checked through a printed log, so that the following problems are brought.
Adding the log requires resending the version, testing and approval of the version, and has long flow, long time consumption and influence on the positioning and repairing timeliness of the problem.
Because of the uncertainty of the problem, one-time publishing may not be able to solve the problem, multiple publishing is required, and logs are added in different code blocks to solve the problem.
Some problem testing environments cannot be verified, and after a problem is repaired, production line verification is necessary, which brings a certain production line risk (because whether the defect is repaired cannot be determined, and other problems may be caused by repairing the defect).
Disclosure of Invention
The disclosure is in part intended to introduce concepts in a simplified form that are further described below in the detailed description. The disclosure is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Some embodiments of the present disclosure propose a production line problem repair method, apparatus, electronic device, and computer-readable medium to solve the technical problems mentioned in the background section above.
In a first aspect, some embodiments of the present disclosure provide a method for repairing a production line problem, the method comprising: acquiring identification information of a user in response to detection of login operation of the user;
judging whether the user is a white list user or not based on the identification information;
assigning the user to a target machine and executing code on the target machine in response to the user being a whitelisted user, wherein the whitelisted user includes problem feedback information for the user;
and modifying the byte code of the code on the target machine based on the hot update code, and repairing the production line problem corresponding to the problem feedback information on the target machine.
In a second aspect, some embodiments of the present disclosure provide a line problem repair apparatus, the apparatus comprising: an acquisition unit, configured to acquire identification information of a user in response to detection of a login operation of the user;
the judging unit is used for judging whether the user is a white list user or not based on the identification information;
an execution unit configured to allocate the user to a target machine and execute a code on the target machine in response to the user being a whitelisted user, wherein the whitelisted user includes problem feedback information for the user;
and the repairing unit is used for repairing the production line problem corresponding to the problem feedback information on the target machine based on the byte code of the code on the target machine modified by the hot update code.
In a third aspect, some embodiments of the present disclosure provide an electronic device comprising: one or more processors; a storage device having one or more programs stored thereon, which when executed by one or more processors, cause the one or more processors to implement the method as in any of the first aspects.
In a fourth aspect, some embodiments of the present disclosure provide a computer readable medium having a computer program stored thereon, wherein the program when executed by a processor implements a method as in any of the first aspects.
One of the above embodiments of the present disclosure has the following advantageous effects: firstly, in response to detection of login operation of a user, acquiring identification information of the user; then, based on the identification information, judging whether the user is a white list user or not; then, in response to the user being a whitelisted user, assigning the user to a target machine and executing code on the target machine, wherein the whitelisted user includes problem feedback information for the user; and finally, modifying the byte code of the code on the target machine based on the hot update code, and repairing the production line problem corresponding to the problem feedback information on the target machine. The implementation method realizes the technology of updating by code heat, can quickly solve the production line problem under the condition of not going through the version release flow, and can not influence the use of other normal users.
Drawings
The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.
FIG. 1 is a flow chart of some embodiments of a production line problem remediation method according to the present disclosure;
FIG. 2 is a flow chart of other embodiments of a line problem remediation method according to the present disclosure;
FIG. 3 is a schematic structural view of some embodiments of a line problem remediation device according to the present disclosure;
fig. 4 is a schematic structural diagram of an electronic device suitable for use in implementing some embodiments of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure.
It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings. Embodiments of the present disclosure and features of embodiments may be combined with each other without conflict.
It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.
It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise.
The names of messages or information interacted between the various devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.
The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 is a flow chart of some embodiments of a line problem remediation method according to the present disclosure. The production line problem repairing method comprises the following steps:
In some embodiments, an execution subject (e.g., may be a server) of the line problem repair method may obtain identification information of a user in response to detecting a login operation of the user. The identification information may be an id of the user, for example, the id of the user may be an account number of the user; as an example, the login operation of the user may be an autonomous login operation of the user on the terminal device, or may be a login operation of the user after receiving the prompt information; the login operation can be triggered by a user aiming at a login control.
In some optional implementations of some embodiments, before the acquiring the identification information of the user in response to detecting the login operation of the user, the method further includes:
responding to the acquired problem feedback information of the user, and acquiring user information of the user; the problem feedback information may be used to describe problems encountered during use, for example, failure of web page refresh, incomplete display of page content, web page jam, payment failure, etc.; the user information may be information that is filled in by the user when registering the account, for example, may be a user name, an account, and the like of the user.
And setting the user corresponding to the user information of the user as a white list user. As an example, when a user uses this item, a problem is encountered or found, the problem is fed back to the customer service, and then the executing body acquires the account of the user, and adds the account to the whitelist of users.
In some embodiments, the executing entity may determine whether the user is a white list user based on the identification information. The white list user can be a preset user account or a later added user account. For example, the account number of the tester issued before the project is formally online may be the account number of the user who receives the user feedback problem after the user is online. As an example, according to the identification information obtained by the identification information, searching whether the same account number exists in the white list user list, if so, the white list user is the white list user, and if not, the white list user is not the white list user.
Step 103, responsive to the user being a whitelisted user, assigning the user to a target machine and executing code on the target machine.
In some embodiments, the executing entity may allocate the user to a target machine and execute code on the target machine in response to the user being a whitelisted user, wherein the whitelisted user includes problem feedback information for the user. The target machine generally refers to a terminal device that a developer can edit, modify, test, and maintain program code. The code on the target machine is generally consistent with the formally online program code.
And step 104, based on the hot update code, modifying the byte code of the code on the target machine, and repairing the production line problem corresponding to the problem feedback information on the target machine.
In some embodiments, the executing entity may modify, on the target machine, a bytecode of a code on the target machine based on a hot update code, and repair a production line problem corresponding to the problem feedback information on the target machine. The execution body can modify the byte code to replace the existing class file, thereby completing the repair of the production line problem. The class file is named as a Java class file, and Java is mainly suitable for a network in terms of platform independence and network mobility. Its tasks in terms of platform independence are: the Java program is provided with a binary form of service independent of the underlying host platform. The hot update code is typically allowed to load the modified program code without restarting the process and to execute correctly as expected.
In some optional implementations of some embodiments, based on the problem feedback information, adding a log for troubleshooting a problem corresponding to the problem feedback information on the target machine; the log for checking the problem corresponding to the problem feedback information may be a log written by a tester according to the received problem feedback information. And determining the position information of the production line problem corresponding to the log based on the log. By adding a log of troubleshooting problems, the problems can be quickly located. Positioning for the production line problematic problem does not need to take a long process to issue version positioning. The code can be updated for a plurality of times, and information such as a log is added.
In some alternative implementations of some embodiments, the user is removed from the whitelisted user list in response to the verification result information being information characterizing verification pass.
Some embodiments of the present disclosure disclose a production line problem repairing method, firstly, in response to detecting a login operation of a user, acquiring identification information of the user; then, based on the identification information, judging whether the user is a white list user or not; then, in response to the user being a whitelisted user, assigning the user to a target machine and executing code on the target machine, wherein the whitelisted user includes problem feedback information for the user; and finally, modifying the byte code of the code on the target machine based on the hot update code, and repairing the production line problem corresponding to the problem feedback information on the target machine. The implementation method realizes the technology of updating by code heat, can quickly solve the production line problem under the condition of not going through the version release flow, and can not influence the use of other normal users.
With further reference to fig. 2, a flow chart of some embodiments of a line problem remediation method according to the present disclosure is provided. The production line problem repairing method comprises the following steps:
in step 201, in response to detecting a login operation of a user, identification information of the user is acquired.
In response to the user being a whitelisted user, the user is assigned to a target machine and code on the target machine is executed, step 203.
And step 204, modifying the byte code of the code on the target machine based on the hot update code, and repairing the production line problem corresponding to the problem feedback information on the target machine.
In some embodiments, the specific implementation of steps 201 to 204 and the technical effects thereof may refer to steps 101 to 104 in those embodiments corresponding to fig. 1, which are not described herein.
In some embodiments, an execution subject (e.g., may be a server) of a line problem remediation method may allocate the user to a line formal machine and execute code on the line formal machine in response to the user not being a whitelisted user. The production line formal machine is terminal equipment for running the project after the project is formally online, and the terminal equipment can be a computer, a mobile phone, a tablet and the like.
And step 206, in response to detecting that the repair for the production line problem is completed, sending login information to the user.
In some embodiments, the executing entity may send login information to the user when detecting that the repair for the line problem is completed. The login information is information for prompting the user that the problem is repaired and completed, and the user can log in again to perform operation.
In step 207, in response to detecting that the user logs in again, the code on the target machine is executed, and an execution result is generated.
In some embodiments, the executing entity may execute code on the target machine in response to detecting the user re-login, generating an execution result. The code on the target machine is the code after the repair has been completed. The execution result may be information about whether the code is successfully run when the user logs in again to perform the operation.
And step 208, determining whether the production line problem is successfully repaired according to the execution result, and generating verification result information.
In some embodiments, the execution body may determine whether the line problem is successfully repaired according to the execution result, and generate verification result information. The verification result information is information for describing whether the line problem is successfully repaired. As an example, if the code is successfully run when the user logs in again to perform the operation, the line problem is successfully repaired, and if the running of the user code is failed, the line problem is failed to repair.
And step 209, synchronizing the code on the target machine to the production line formal machine in response to the verification result information being information for representing that verification is passed.
In some embodiments, the executing entity may synchronize the code on the target machine to the production line formal machine in response to the verification result information being information characterizing verification pass.
Some embodiments of the disclosure disclose a method for repairing a production line problem, which implements a technology of combining whitelist splitting and code hot updating on the basis of the embodiment described in fig. 1, and can add a log for troubleshooting the problem without going through a version release process, quickly locate and solve the problem, and ensure that the use of other normal users is not affected during the process of repairing and debugging the problem through whitelist control.
With further reference to fig. 3, as an implementation of the method shown in the above figures, the present disclosure provides some embodiments of a vehicle picture background blurring apparatus, which correspond to those method embodiments shown in fig. 1, and which are particularly applicable in various electronic devices.
As shown in fig. 3, the line problem repair apparatus 300 of some embodiments includes: an acquiring unit 301, a judging unit 302, an executing unit 303 and a repairing unit 304, wherein the acquiring unit 301 is configured to acquire identification information of a user in response to detection of a login operation of the user; a judging unit 302, configured to judge whether the user is a white list user based on the identification information; an execution unit 303, configured to allocate the user to a target machine in response to the user being a whitelisted user, and execute a code on the target machine, where the whitelisted user includes problem feedback information of the user; and the repairing unit 304 is configured to repair a production line problem corresponding to the problem feedback information on the target machine based on the byte code of the code on the target machine modified by the hot update code.
Some embodiments of the present disclosure disclose an apparatus that, first, in response to detecting a login operation of a user, acquires identification information of the user; then, based on the identification information, judging whether the user is a white list user or not; then, in response to the user being a whitelisted user, assigning the user to a target machine and executing code on the target machine, wherein the whitelisted user includes problem feedback information for the user; and finally, modifying the byte code of the code on the target machine based on the hot update code, and repairing the production line problem corresponding to the problem feedback information on the target machine. The implementation method realizes the technology of combining white list splitting and code hot updating, can quickly locate and solve the problem under the condition of not going through the version release flow, and can not influence the use of other normal users.
In an alternative implementation of some embodiments, the line problem repair apparatus 300 further includes, before the acquiring unit 301: the user information acquisition unit is used for responding to the acquired problem feedback information of the user and acquiring the user information of the user; and the setting unit is used for setting the user corresponding to the user information of the user as a white list user.
In an alternative implementation of some embodiments, after obtaining the problem feedback information of the user, the production line problem repair device 300 is further configured to: based on the problem feedback information, adding a log for checking problems corresponding to the problem feedback information on the target machine; and determining the position information of the production line problem corresponding to the log based on the log.
In an alternative implementation of some embodiments, the production line problem repair device 300, after the repair unit 304, is further configured to: in response to detecting completion of repair for the production line problem, sending login information to the user; executing code on the target machine in response to detecting the user re-login, generating an execution result; and determining whether the production line problem is successfully repaired according to the execution result, and generating verification result information.
In an alternative implementation of some embodiments, the line problem repairing apparatus 300 is further configured, after determining whether the line problem is repaired successfully according to the execution result, to generate verification result information, to: and in response to the user not being a whitelist user, assigning the user to a line formal machine and executing code on the line formal machine.
In an alternative implementation of some embodiments, the production line problem remediation device 300 is further configured to: and in response to the user not being a whitelist user, assigning the user to a line formal machine and executing code on the line formal machine.
In an alternative implementation of some embodiments, the line problem repairing apparatus 300 is further configured, after determining whether the line problem is repaired successfully according to the execution result, to generate verification result information, to: and in response to the verification result information being information for representing that verification is passed, removing the user from a whitelist of users.
It will be appreciated that the elements described in the apparatus 300 correspond to the various steps in the method described with reference to fig. 1. Thus, the operations, features and resulting benefits described above with respect to the method are equally applicable to the apparatus 300 and the units contained therein, and are not described in detail herein.
In this embodiment, referring to fig. 4, a schematic structural diagram of an electronic device is provided.
As shown in fig. 4, the electronic device 400 may include a processor 420 and a memory 410, the memory 410 for storing executable instructions; the processor 420 is configured to run the electronic device according to control of the instructions to perform the method according to any embodiment of the present disclosure.
It should be noted that, in some embodiments of the present disclosure, the computer readable medium may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In some embodiments of the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In some embodiments of the present disclosure, however, the computer-readable signal medium may comprise a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.
In some implementations, the clients, servers may communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol ), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the internet (e.g., the internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.
The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: acquiring identification information of a user in response to detection of login operation of the user; judging whether the user is a white list user or not based on the identification information; assigning the user to a target machine and executing code on the target machine in response to the user being a whitelisted user, wherein the whitelisted user includes problem feedback information for the user; and modifying the byte code of the code on the target machine based on the hot update code, and repairing the production line problem corresponding to the problem feedback information on the target machine.
Computer program code for carrying out operations for some embodiments of the present disclosure may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or 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/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, 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.
The units described in some embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. The described units may also be provided in a processor, for example, described as: a processor includes an acquisition unit, a determination unit, an execution unit, and a repair unit. The names of these units do not constitute a limitation on the unit itself in some cases, and for example, the acquisition unit may also be described as "a unit that acquires identification information of a user in response to detection of a login operation of the user".
The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.
The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by those skilled in the art that the scope of the invention in the embodiments of the present disclosure is not limited to the specific combination of the above technical features, but encompasses other technical features formed by any combination of the above technical features or their equivalents without departing from the spirit of the invention. Such as the above-described features, are mutually substituted with (but not limited to) the features having similar functions disclosed in the embodiments of the present disclosure.
Claims (10)
1. A production line problem repair method, comprising:
acquiring identification information of a user in response to detection of login operation of the user;
judging whether the user is a white list user or not based on the identification information;
assigning the user to a target machine and executing code on the target machine in response to the user being a whitelisted user, wherein the whitelisted user includes problem feedback information for the user;
and modifying the byte code of the code on the target machine based on the hot update code, and repairing the production line problem corresponding to the problem feedback information on the target machine.
2. The method of claim 1, wherein prior to the acquiring the identification information of the user in response to detecting a login operation of the user, the method further comprises:
responding to the acquired problem feedback information of the user, and acquiring user information of the user;
and setting the user corresponding to the user information of the user as a white list user.
3. The method of claim 2, further comprising, after the obtaining of the user's question feedback information:
based on the problem feedback information, adding a log for checking problems corresponding to the problem feedback information on the target machine;
and determining the position information of the production line problem corresponding to the log based on the log.
4. The method of claim 1, wherein after the modifying the bytecode of the code on the target machine based on the hot update code on the target machine, repairing a production line problem corresponding to the problem feedback information on the target machine, the method further comprises:
in response to detecting completion of repair for the production line problem, sending login information to the user;
executing code on the target machine in response to detecting the user re-login, generating an execution result;
and determining whether the production line problem is successfully repaired according to the execution result, and generating verification result information.
5. The method of claim 4, wherein after the determining whether the line problem is successfully repaired based on the execution result, generating verification result information, the method further comprises:
and synchronizing the code on the target machine to the production line formal machine in response to the verification result information being information for representing that verification is passed.
6. The method according to claim 1, wherein the method further comprises:
and in response to the user not being a whitelist user, assigning the user to a line formal machine and executing code on the line formal machine.
7. The method of claim 4, wherein after said determining whether said line problem is successfully repaired based on said execution result, generating verification result information, said method further comprises;
and in response to the verification result information being information for representing that verification is passed, removing the user from a whitelist of users.
8. A production line problem remediation device comprising:
an acquisition unit, configured to acquire identification information of a user in response to detection of a login operation of the user;
the judging unit is used for judging whether the user is a white list user or not based on the identification information;
an execution unit configured to allocate the user to a target machine and execute a code on the target machine in response to the user being a whitelisted user, wherein the whitelisted user includes problem feedback information for the user;
and the repairing unit is used for repairing the production line problem corresponding to the problem feedback information on the target machine based on the byte code of the code on the target machine modified by the hot update code.
9. An electronic device, comprising:
a memory for storing executable instructions;
a processor for executing the method according to any of claims 1-7, according to control of the instructions, by the electronic device.
10. A computer readable medium having stored thereon a computer program, wherein the program when executed by a processor implements the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310158466.3A CN116048590A (en) | 2023-02-16 | 2023-02-16 | Production line problem repairing method, device, electronic equipment and computer readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310158466.3A CN116048590A (en) | 2023-02-16 | 2023-02-16 | Production line problem repairing method, device, electronic equipment and computer readable medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116048590A true CN116048590A (en) | 2023-05-02 |
Family
ID=86127413
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310158466.3A Pending CN116048590A (en) | 2023-02-16 | 2023-02-16 | Production line problem repairing method, device, electronic equipment and computer readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116048590A (en) |
-
2023
- 2023-02-16 CN CN202310158466.3A patent/CN116048590A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111045756B (en) | Method, apparatus, computing device and medium for generating interface service | |
| CN112650685B (en) | Automatic test method, device, electronic equipment and computer storage medium | |
| US20190087307A1 (en) | Method and apparatus for developing unmanned vehicle application | |
| US10698797B2 (en) | Mobile application program testing method, server, terminal, and storage medium | |
| US7996818B1 (en) | Method for testing using client specified references | |
| CN109684188B (en) | Test method and device | |
| CN108459850B (en) | Method, device and system for generating test script | |
| US20170109257A1 (en) | Use case driven stepping component automation framework | |
| CN110851471A (en) | Distributed log data processing method, device and system | |
| CN111367531B (en) | Code processing method and device | |
| CN107621963B (en) | Software deployment method, software deployment system and electronic equipment | |
| CN113687858A (en) | Configuration file checking method and device, electronic equipment and storage medium | |
| CN116069341A (en) | Automatic deployment method, equipment and storage medium for application program | |
| CN107632909B (en) | Method and system for automatically testing device functions | |
| CN110727575B (en) | Information processing method, system, device and storage medium | |
| CN109299124B (en) | Method and apparatus for updating a model | |
| US20160085659A1 (en) | Base Line for Code Analysis | |
| CN109218338B (en) | Information processing system, method and device | |
| CN116048590A (en) | Production line problem repairing method, device, electronic equipment and computer readable medium | |
| CN110727945B (en) | Virus scanning method, device and computer readable medium | |
| CN113360365B (en) | Flow test method and flow test system | |
| CN112783903B (en) | Method and device for generating update log | |
| CN112882921B (en) | Fault simulation method and device | |
| CN112084114A (en) | Method and apparatus for testing an interface | |
| CN117112435B (en) | Vulnerability linkage detection result fusion method, storage medium and electronic equipment |
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 |