Method, device, electronic device and storage medium for automatically restoring call stack

Abstract

The present invention discloses a method, device, electronic device and storage medium for automatically restoring a call stack, the method comprising the steps of: obtaining the installation information of a front-end packaging tool plug-in and the configured trigger environment variable information; obtaining the information of the front-end packaging tool plug-in completing the configuration and the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in according to the installation information of the front-end packaging tool plug-in and the configured trigger environment variable information; obtaining the wrong call stack according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, decompiling the source code fragment of the wrong call stack through the source code and compiled code mapping relationship file. The present application can automatically decode the wrong call stack, so that the developer does not need to care about the wrong call stack decoding process, does not need to manage the SourceMap file, has no possibility of exposing the source code, and does not have compatibility issues.

Description

Technical Field

[0001] The present invention relates to the field of software technology, and in particular to a method, device, electronic device and storage medium for automatically restoring a call stack. Background Art

[0002] The mapping relationship file between source code and compiled code (SourceMap) originated from Closure Compile, a js (JavaScript, interpreter) compression tool of Google. It was invented to correspond to Closure Inspector, a source code level debugging tool. It is an information file that stores the mapping relationship between source code and compiled code. SourceMap was developed as an auxiliary tool, but because JavaScript scripts are becoming more and more complex, it has become the main technology of front-end development and has been written into browsers, because most source codes must be converted before they can be put into production environments. When the square function in the production environment reports an error, since the source code of the error cannot be located, SourceMap is used to record the source code translation position information and character change information, so that when the error occurs, the source code can be decompiled through SourceMap to accurately locate the actual row and column position of the file where the error is located. In the prior art, this method has the problem that although the row and column position of the error can be found, anyone can get the software source code through the browser, which may leak trade secrets. At the same time, different browsers have different support for SourceMap. Some browsers cannot accurately restore the source code situation. Sometimes there are problems such as not being able to automatically decompile and requiring manual intervention.

[0003] Therefore, a method for automatically restoring a call stack is needed, which can store the source code and compiled code mapping relationship file according to the strategy, and decompile the source code and compiled code mapping relationship file when obtaining an erroneous call stack to obtain the source code fragment of the erroneous call stack. Summary of the invention

[0004] To this end, the present invention provides a method, device, electronic device and storage medium for automatically restoring a call stack, in an effort to solve or at least alleviate at least one of the above problems.

[0005] According to one aspect of the present invention, a method for automatically restoring a call stack is provided. The method uses a front-end packaging tool plug-in to store a source code and compiled code mapping relationship file according to a policy. When obtaining an erroneous call stack, the source code and compiled code mapping relationship file is used for decompilation to obtain a source code fragment of the erroneous call stack. The method comprises the steps of:

[0006] Obtain the installation information of the front-end packaging tool plug-in and the configured trigger environment variable information; obtain the configuration completion information of the front-end packaging tool plug-in based on the installation information and the configured trigger environment variable information of the front-end packaging tool plug-in; obtain the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in based on the configuration completion information and source code of the front-end packaging tool plug-in; obtain the erroneous call stack based on the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, and obtain the source code fragment of the erroneous call stack by decompiling the source code and compiled code mapping relationship file.

[0007] In another embodiment, the step of obtaining information on the completion of configuration of the front-end packaging tool plug-in based on the installation information and configured trigger environment variable information of the front-end packaging tool plug-in includes: obtaining information on the trigger startup of the front-end packaging tool plug-in; obtaining information on the developer tool of the front-end packaging tool plug-in being set to only hide source code mode based on the trigger startup information of the front-end packaging tool plug-in; obtaining address information of the source file in the source code and compiled code mapping relationship file of the front-end packaging tool plug-in that does not contain the source code and compiled code mapping relationship file based on the developer tool of the front-end packaging tool plug-in being set to only hide source code mode information; obtaining information on the front-end packaging tool plug-in introducing external plug-ins and starting work based on the trigger startup information of the front-end packaging tool plug-in.

[0008] In another embodiment, the steps of introducing external plug-in information and starting work of the front-end packaging tool plug-in include: obtaining the front-end packaging tool plug-in completion configuration information; obtaining the error call stack capture software development tool kit based on the front-end packaging tool plug-in completion configuration information; obtaining the source code and compiled code mapping relationship file upload information based on the error call stack capture software development tool kit; obtaining the upload class initialization information of the simple storage service based on the source code and compiled code mapping relationship file upload information; obtaining the operation security environment check information of the front-end packaging tool plug-in based on the operation security environment check information of the front-end packaging tool plug-in According to the information, the front-end packaging tool plug-in build success response hook information is obtained; according to the front-end packaging tool plug-in build success response hook information, the file path list information of the source code and compiled code mapping relationship file is obtained; according to the file path list information of the source code and compiled code mapping relationship file, the uploaded source code and compiled code mapping relationship file and the corresponding JavaScript file with the same name are obtained; according to the uploaded source code and compiled code mapping relationship file and the corresponding JavaScript file with the same name, the source code and compiled code mapping relationship file uploaded according to the set directory rules are obtained, and the source code is automatically injected by the error call stack capture software development kit.

[0009] In another embodiment, the step of obtaining the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in based on the configuration information and source code completed by the front-end packaging tool plug-in includes: obtaining the release pipeline in the local development environment based on the configuration information completed by the front-end packaging tool plug-in; obtaining the packaging and processing of data by the production pipeline through the front-end packaging tool plug-in based on the release pipeline in the local development environment; obtaining the production pipeline to deploy an online program package to the production server based on the packaging and processing result of the data by the front-end packaging tool plug-in, and uploading the source code and compiled code mapping relationship file to the internal server of this end; deploying the online program package to the production server based on the production pipeline, and uploading the source code and compiled code mapping relationship file to the internal server of this end, and the internal server storing the source code and compiled code mapping relationship file to the content distribution network server.

[0010] In another embodiment, the step of obtaining an erroneous call stack and decompiling the source code snippet of the erroneous call stack through the source code and compiled code mapping relationship file according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in includes: obtaining the erroneous call stack in the source code and compiled code mapping relationship file according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in; obtaining the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in according to the erroneous call stack in the source code and compiled code mapping relationship file; obtaining the code snippet of the source file of the erroneous call stack according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in; decompiling the source code and compiled code mapping relationship file to obtain source code information when obtaining the call stack according to the code snippet of the source file of the erroneous call stack.

[0011] In another embodiment, the step of obtaining the code snippet of the source file of the erroneous call stack based on the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in includes: obtaining the erroneous call stack information and interface verification information; obtaining the line number, column number, source file name and content of the erroneous call stack based on the erroneous call stack information and interface verification information; obtaining the storage strategy of the front-end packaging tool plug-in to download the source code and compiled code mapping relationship file corresponding to the erroneous call stack based on the line number, column number, source file name and content, and interface verification information of the erroneous call stack; downloading the source code and compiled code mapping relationship file corresponding to the erroneous call stack based on the storage strategy of the front-end packaging tool plug-in to obtain the source file corresponding to the erroneous call stack; obtaining the code snippet of the source file of the erroneous call stack based on the source file corresponding to the erroneous call stack.

[0012] According to another aspect of the present invention, a method for automatically restoring a call stack is disclosed, the steps of the method comprising: a client accesses a production server and obtains web page data returned by the production server, and the client installs a front-end packaging tool plug-in; based on the web page data returned by the production server obtained by the client, erroneous call stack information in the web page data is obtained; based on the erroneous call stack information in the web page data, an internal server of the client obtains source code and compiled code mapping relationship file information from a content distribution network according to a set storage policy; based on the source code and compiled code mapping relationship file obtained by the internal server, the internal server obtains the row and column numbers of the erroneous call stack and the source code position where the erroneous call stack parsing error is located; based on the row and column numbers of the erroneous call stack obtained by the internal server and the source code position where the erroneous call stack parsing error is located, an erroneous source code fragment of the erroneous call stack is obtained.

[0013] According to another aspect of the present invention, a device for automatically restoring a call stack is disclosed. The device uses a front-end packaging tool plug-in to store according to a strategy of a source code and a compiled code mapping relationship file. When obtaining an erroneous call stack, the device performs decompilation through the source code and the compiled code mapping relationship file to obtain a source code fragment of the erroneous call stack. The device comprises: a plug-in acquisition module, which is used to obtain installation information of the front-end packaging tool plug-in and configured trigger environment variable information; a storage control module, which is used to obtain information on the completion of configuration of the front-end packaging tool plug-in based on the installation information and configured trigger environment variable information of the front-end packaging tool plug-in; based on the information on the completion of configuration of the front-end packaging tool plug-in and the source code, obtain the storage strategy of the source code and the compiled code mapping relationship file of the front-end packaging tool plug-in; a call stack restoration module, which is used to obtain an erroneous call stack according to the storage strategy of the source code and the compiled code mapping relationship file of the front-end packaging tool plug-in, and decompile the source code and the compiled code mapping relationship file to obtain the source code fragment of the erroneous call stack.

[0014] According to another aspect of the present invention, a computing device is provided, comprising: one or more processors; and a memory; one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions for executing any of the methods for automatically restoring a call stack as described above.

[0015] According to another aspect of the present invention, a computer-readable storage medium storing one or more programs is provided, wherein the one or more programs include instructions, which, when executed by a computing device, enable the computing device to perform any of the methods for automatically restoring a call stack as described above.

[0016] According to the solution of automatic call stack restoration of the present invention, the installation information and configuration trigger environment variable information of the front-end packaging tool plug-in are obtained; according to the installation information and configuration trigger environment variable information of the front-end packaging tool plug-in, the configuration information of the front-end packaging tool plug-in is obtained; according to the configuration information and source code of the front-end packaging tool plug-in, the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in is obtained; according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, the wrong call stack is obtained, and the source code fragment of the wrong call stack is obtained by decompiling the source code and compiled code mapping relationship file. The present application can automatically decode the wrong call stack, so that the developer does not need to care about the wrong call stack decoding process, does not need to manage the SourceMap file, only needs to configure once, there is no possibility of exposing the source code, and there is no compatibility problem. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] To achieve the above and related purposes, certain illustrative aspects are described herein in conjunction with the following description and accompanying drawings, which indicate various ways in which the principles disclosed herein can be practiced, and all aspects and their equivalents are intended to fall within the scope of the claimed subject matter. The above and other purposes, features and advantages of the present disclosure will become more apparent by reading the following detailed description in conjunction with the accompanying drawings. Throughout the present disclosure, the same reference numerals generally refer to the same parts or elements.

[0018] Figure 1 A schematic diagram showing the structure of a computing device 100 according to an embodiment of the present invention; and

[0019] Figure 2 A flowchart showing a method 200 for automatically restoring a call stack according to an embodiment of the present invention; and

[0020] Figure 3 A flowchart showing another embodiment of a method for automatically restoring a call stack according to an embodiment of the present invention; and

[0021] Figure 4 A flowchart showing another embodiment of a method for automatically restoring a call stack according to an embodiment of the present invention; and

[0022] Figure 5 A schematic structural diagram of an apparatus 300 for automatically restoring a call stack according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0023] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0024] Figure 1 1 is a block diagram of an example computing device 100. In a basic configuration 102, computing device 100 typically includes a system memory 106 and one or more processors 104. A memory bus 108 may be used for communication between processor 104 and system memory 106.

[0025] Depending on the desired configuration, the processor 104 can be any type of processor, including but not limited to: a microprocessor (μP), a microcontroller (μC), a digital information processor (DSP), or any combination thereof. The processor 104 can include one or more levels of cache such as a first-level cache 110 and a second-level cache 112, a processor core 114, and registers 116. An example processor core 114 can include an arithmetic logic unit (ALU), a floating point unit (FPU), a digital signal processing core (DSP core), or any combination thereof. An example memory controller 118 can be used with the processor 104, or in some implementations, the memory controller 118 can be an internal part of the processor 104.

[0026] Depending on the desired configuration, the system memory 106 may be any type of memory, including but not limited to: volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. The system memory 106 may include an operating system 120, one or more applications 122, and program data 124. In some embodiments, the application 122 may be arranged to operate on the operating system using the program data 124. In some embodiments, the computing device 100 is configured to execute a method 200 for automatically restoring a call stack, and the method 200 can be stored according to the strategy of the source code and compiled code mapping relationship file through a front-end packaging tool plug-in, and when obtaining an erroneous call stack, the source code and compiled code mapping relationship file are decompiled to obtain a source code fragment of the erroneous call stack, and the program data 124 includes instructions for executing the method 200.

[0027] The computing device 100 may also include an interface bus 140 that facilitates communication from various interface devices (e.g., output devices 142, peripheral interfaces 144, and communication devices 146) to the basic configuration 102 via the bus / interface controller 130. Example output devices 142 include a graphics processing unit 148 and an audio processing unit 150. They can be configured to facilitate communication with various external devices such as a display or speakers via one or more A / V ports 152. Example peripheral interfaces 144 may include a serial interface controller 154 and a parallel interface controller 156, which may be configured to facilitate communication with external devices such as input devices (e.g., keyboards, mice, pens, voice input devices, touch input devices) or other peripherals (e.g., printers, scanners, etc.) via one or more I / O ports 158. Example communication devices 146 may include a network controller 160, which may be arranged to facilitate communication with one or more other computing devices 162 via a network communication link via one or more communication ports 164.

[0028] A network communication link can be an example of a communication medium. The communication medium can generally be embodied as a computer-readable instruction, data structure, program module in a modulated data signal such as a carrier wave or other transmission mechanism, and can include any information delivery medium. A "modulated data signal" can be such a signal, one or more of which or its changes in a data set can be performed in a manner that encodes information in the signal. As a non-limiting example, the communication medium may include a wired medium such as a wired network or a dedicated line network, and various wireless media such as sound, radio frequency (RF), microwave, infrared (IR) or other wireless media. The term computer-readable medium used here may include both storage media and communication media. In some embodiments, one or more programs are stored in a computer-readable medium, and the one or more programs include instructions for executing certain methods, such as according to an embodiment of the present invention, the computing device 100 executes the method 200 of automatically restoring the call stack through the instructions.

[0029] The computing device 100 may be implemented as part of a small-sized portable (or mobile) electronic device, such as a cellular phone, a personal digital assistant (PDA), a personal media player device, a wireless network browsing device, a personal head-mounted device, an application-specific device, or a hybrid device that may include any of the above functions. The computing device 100 may also be implemented as a personal computer including desktop and notebook computer configurations.

[0030] In the prior art, common source code conversions are mainly the following four situations: compression to reduce the size; merging multiple files to reduce the number of HTTP requests; compiling other languages ​​into JavaScript; and transcoding. In all four cases, the actual running code is different from the development code, making it difficult to locate the problem. Usually, the JavaScript interpreter will tell you the line and column where the code is wrong. However, this is useless for the converted code.

[0031] The existing technical solutions mainly include the following typical solutions:

[0032] When the software is released and built, the generated online package and SourceMap file are uploaded to the production environment at the same time, and the corresponding SourceMap file address is added to the end of the online package, such as CSS and JavaScript files. The source code is automatically decompiled through the browser's built-in SourceMap decoder, which makes it easy to decode the source code of the error call stack. The disadvantage of this method is that the source code is exposed. Anyone can get the software source code through the browser, thereby leaking company secrets; different browsers have different support for SourceMap, and some browsers may not be able to accurately restore the source code.

[0033] When the software is in the release build phase, the online package and SourceMap file are generated at the same time, and the online package is released to the production environment. The SourceMap file is retained locally, and the corresponding SourceMap file address is not added to the end of the online package. When the browser displays an error call stack information, local decompilation is performed through other SourceMap tools to obtain the source code location information. The disadvantages of this method are: it is not automated, and requires manual intervention and manual execution of the SourceMap decompilation program; the version is difficult to manage, and multiple versions of the local SourceMap file may appear; the local SourceMap version is inconsistent with the online package build version.

[0034] Specifically, in a project development, the module platforms involved mainly include the client, which is used to access data; the production server, which is used to provide data services to the client; the internal server, which is used to provide data services to the production server; the monitoring platform, which is used to monitor the data service quality on the client, production server, and internal server; the content distribution network server, which is used to distribute and store data provided by users. On the client side, it also includes the local development environment, which is used to provide desktop software for program development and design; and the production assembly line, which is used to publish the designed software development and design program to the production server.

[0035] Figure 2FIG. 2 is a flow chart of a method 200 for automatically restoring a call stack according to an embodiment of the present invention. Figure 2 As shown, the method 200 method uses a front-end packaging tool plug-in to store the source code and compiled code mapping relationship file according to the strategy, and decompiles the source code and compiled code mapping relationship file when obtaining an erroneous call stack to obtain the source code fragment of the erroneous call stack. The method 200 starts at step S210 to obtain the installation information of the front-end packaging tool plug-in and the configured trigger environment variable information.

[0036] Specifically, the front-end packaging tool plug-in is a Webpack plug-in. When a developer develops a project, he first uses the command line to install the Webpack plug-in in the project, which is the front-end packaging tool plug-in. The Webpack plug-in is an open source front-end packaging tool that provides a modular development method that is lacking in front-end development. It treats various static resources as modules and generates optimized code from them. The installation code of the front-end packaging tool plug-in is: nmpi@dlrarc / ftwo-webpack-plugin–D

[0037] At the same time, the developer needs to configure the corresponding environment variables in npm scripts to trigger the front-end packaging tool plug-in to work. In the embodiment of the present application, the environment variable is FTWO=production, and the corresponding program code is:

[0038]

[0039] Through step S220, information on the completion of configuration of the front-end packaging tool plug-in is obtained based on the installation information of the front-end packaging tool plug-in and the configured trigger environment variable information.

[0040] Specifically, after completing the installation of the front-end packaging tool plug-in and configuring the triggering environment variables, the front-end packaging tool plug-in can be configured to enable the front-end packaging tool plug-in to work in a corresponding working mode.

[0041] Specifically, in one embodiment of the present application, the step of obtaining the information of the front-end packaging tool plug-in completing the configuration according to the installation information of the front-end packaging tool plug-in and the configured trigger environment variable information includes:

[0042] Obtaining the information for triggering the startup of the front-end packaging tool plug-in;

[0043] According to the information of triggering the start of the front-end packaging tool plug-in, the developer tool of the front-end packaging tool plug-in is set to hide the source code mode information only; specifically, the application name corresponding to the developer tool of the front-end packaging tool plug-in is devtool, and devtool is configured as hidden-source-map, and the hidden-source-map is a hidden source code mode only. In this mode, the error cause of the error code can be displayed, but there is no error location, the error source code cannot be traced, and only the error location of the built code can be prompted.

[0044] According to the setting of the developer tool of the front-end packaging tool plug-in to only hide the source code mode information, the source code and compiled code mapping relationship file of the front-end packaging tool plug-in is obtained, and the source file does not contain the address information of the source code and compiled code mapping relationship file; specifically, after the developer tool of the front-end packaging tool plug-in is set to only hide the source code mode, when the front-end packaging tool plug-in packages and generates the source code and compiled code mapping relationship file, the source file will not carry the source code and compiled code mapping relationship file address.

[0045] According to the information triggered by the front-end packaging tool plug-in, obtain the information of the front-end packaging tool plug-in introducing external plug-in and start working. Specifically, the application name corresponding to the external plug-in introduced by the front-end packaging tool plug-in is plugins, and the core front-end packaging tool plug-in introduced in the plugins configuration of the front-end packaging tool plug-in is: @dlrarc / ftwo-webpack-plugin. The specific program code is:

[0046]

[0047]

[0048] At this point, the developer runs the product build command npm run build on the production pipeline, and the integrated plug-in @dlrarc / ftwo-webpack-plugin starts working.

[0049] Specifically, in one embodiment of the present application, the steps of the front-end packaging tool plug-in introducing external plug-in information and starting to work, that is, the workflow of @dlrarc / ftwo-webpack-plugin includes:

[0050] Obtain the front-end packaging tool plug-in to complete the configuration information; specifically, it is necessary to complete the initialization configuration of the front-end packaging tool plug-in and complete the initialization of the plug-in.

[0051] Complete the configuration information according to the front-end packaging tool plug-in and obtain the wrong call stack capture software development tool kit; specifically, the wrong call stack capture software development tool kit is also the wrong call stack capture sdk, and the wrong call stack capture software development tool kit is a functional module of the front-end packaging tool plug-in. The purpose of this step is to ensure that the wrong call stack capture software development tool kit can be installed correctly, so that the front-end packaging tool plug-in has the ability to capture the wrong call stack.

[0052] According to the erroneous call stack capture software development toolkit, the source code and compiled code mapping relationship file upload information is obtained; specifically, after the front-end packaging tool plug-in has the erroneous call stack capture capability, the source code and compiled code mapping relationship file also needs to be uploaded to the set database so that the corresponding data service can be provided normally.

[0053] According to the source code and compiled code mapping relationship file upload information, the upload class initialization information of the simple storage service is obtained; specifically, the simple storage service is S3 (Simple Storage Service), which is an object storage with a simple Web service interface that can be used to store and retrieve any amount of data anywhere on the Web. It can provide 99.9999999999% persistence and can deliver trillions of objects on a large scale around the world. Clients use S3 for batch repositories, "data lakes", analysis, backup and restore, disaster recovery and serverless computing, and many native cloud applications even use S3 as primary storage. The upload class initialization of the simple storage service is used to upload the source code and compiled code mapping relationship file to a specified storage space location.

[0054] According to the upload class initialization information of the simple storage service, the operation safety environment check information of the front-end packaging tool plug-in is obtained; specifically, the operation safety environment check is to check whether the network environment of the data service can provide normal data transmission services.

[0055] According to the operation security environment check information of the front-end packaging tool plug-in, the construction success response hook information of the front-end packaging tool plug-in is obtained; specifically, this step includes injecting the hook of the front-end packaging tool plug-in into an event, and then the front-end packaging tool plug-in constructs a successful response hook. The hook injection event and the successful response hook are for obtaining the path of file transfer.

[0056] According to the successful response hook information of the front-end packaging tool plug-in, the file path list information of the source code and compiled code mapping relationship file is obtained;

[0057] According to the file path list information of the source code and compiled code mapping relationship file, the uploaded source code and compiled code mapping relationship file and the corresponding JavaScript file with the same name are obtained; specifically, through this step, the correspondence between the JavaScript file before compilation and the source code and compiled code mapping relationship file after compiling the JavaScript file can be obtained.

[0058] According to the uploaded source code and compiled code mapping relationship file and the corresponding JavaScript file with the same name, the source code and compiled code mapping relationship file are uploaded according to the set directory rules, and the wrong call stack capture software development kit automatically injects the source code. The specific directory rules are implemented by the appkey function module of the front-end packaging tool plug-in. At this time, the appkey function module of the front-end packaging tool plug-in uploads the source code and compiled code mapping relationship file to the internal server according to the set directory rules. If the upload is successful, the constructed source code and compiled code mapping relationship file can be deleted, and the wrong call stack capture software development kit automatically injects the source code.

[0059] Through step S230, according to the configuration information and source code of the front-end packaging tool plug-in, the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in is obtained.

[0060] Specifically, the storage strategy of the source code and compiled code mapping relationship file is to facilitate the management of the source code and compiled code mapping relationship file, while allowing developers to not worry about version issues of the source code and compiled code mapping relationship file. Once erroneous call stack information is received, the source code information can be obtained by decompiling the source code and compiled code mapping relationship file.

[0061] like Figure 3 As shown, specifically, in one embodiment of the present application, the step of obtaining the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in according to the configuration information and source code of the front-end packaging tool plug-in includes:

[0062] According to the information of completing the configuration of the front-end packaging tool plug-in, obtain the release pipeline in the local development environment;

[0063] According to the release pipeline in the local development environment, the production pipeline is obtained to package the data through the front-end packaging tool plug-in;

[0064] According to the result of data packaging processing by the production line through the front-end packaging tool plug-in, the production line deploys an online program package to the production server, and uploads the source code and compiled code mapping relationship file to the internal server of the local end;

[0065] The online program package is deployed to the production service end according to the production pipeline, and the source code and compiled code mapping relationship file is uploaded to the internal server of the local end, and the internal server stores the source code and compiled code mapping relationship file to the content distribution network server.

[0066] It should be noted that Figure 3 It is an overall timing diagram of the development environment for developers to compile software. When the developer compiles the software, after the developed software program is packaged by the front-end packaging tool plug-in, the step of storing the source code and the compiled code mapping relationship file is performed according to the storage strategy of the source code and compiled code mapping relationship file. In this embodiment, the local development environment includes a programming tool for the developer to develop the software program, and a front-end packaging tool plug-in for packaging the completed software program. The production line includes a packaging operation for the software program, and uploading the packaged software program to the local production server. The local production server is used to store the packaged software program completed by the developer. At the same time, the production line also needs to upload the source code and the compiled code mapping relationship file to the internal server. The internal server provides data services for the software program developed by the developer. The internal server uploads and stores the source code and the compiled code mapping relationship file to the content distribution network server, so that when the content distribution network server obtains the data access request of the external terminal, it can provide corresponding data services, and when the wrong call stack information is obtained, the source code corresponding to the wrong call stack can be obtained from the internal server in time.

[0067] Through step S240, according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, the erroneous call stack is obtained by decompiling the source code and compiled code mapping relationship file to obtain the source code fragment of the erroneous call stack.

[0068] Specifically, when the product build command npm run build is run on the production line, the front-end packaging tool plug-in introduces the external plug-in @dlrarc / ftwo-webpack-plugin to start working. If an erroneous call stack occurs during the running process, the source code and compiled code mapping relationship file is used to decompile and obtain the source code fragment of the erroneous call stack.

[0069] Specifically, in one embodiment of the present application, the step of obtaining an erroneous call stack and decompiling the source code and compiling code mapping relationship file to obtain a source code fragment of the erroneous call stack according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in includes:

[0070] According to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, obtaining the call stack of the error in the source code and compiled code mapping relationship file;

[0071] According to the call stack of the error in the source code and compiled code mapping relationship file, obtain the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in;

[0072] According to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, a code snippet of the source file of the erroneous call stack is obtained;

[0073] According to the code snippet of the source file of the erroneous call stack, the source code and compiled code mapping relationship file is decompiled to obtain source code information when obtaining the call stack.

[0074] Specifically, in one embodiment of the present application, the step of obtaining a code snippet of the source file of the erroneous call stack according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in includes:

[0075] Get the error call stack information and interface verification information; specifically, the interface verification is appkey, and the appkey is the API interface verification serial number, which is used to verify the legitimacy of API access.

[0076] Obtain the line number, column number, source file name and content of the erroneous call stack according to the erroneous call stack information and interface verification information;

[0077] According to the line number, column number, source file name and content of the erroneous call stack, and interface verification information, the storage strategy of the front-end packaging tool plug-in is obtained to download the source code and compiled code mapping relationship file corresponding to the erroneous call stack;

[0078] Download the source code and compiled code mapping relationship file corresponding to the erroneous call stack according to the storage strategy of the front-end packaging tool plug-in, and obtain the source file corresponding to the erroneous call stack;

[0079] According to the source file corresponding to the erroneous call stack, a code snippet of the source file of the erroneous call stack is obtained.

[0080] According to the solution of automatic call stack restoration of the present invention, the installation information and configuration trigger environment variable information of the front-end packaging tool plug-in are obtained; according to the installation information and configuration trigger environment variable information of the front-end packaging tool plug-in, the configuration information of the front-end packaging tool plug-in is obtained; according to the configuration information and source code of the front-end packaging tool plug-in, the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in is obtained; according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, the wrong call stack is obtained, and the source code fragment of the wrong call stack is obtained by decompiling the source code and compiled code mapping relationship file. The present application can automatically decode the wrong call stack, so that the developer does not need to care about the wrong call stack decoding process, does not need to manage the SourceMap file, only needs to configure once, there is no possibility of exposing the source code, and there is no compatibility problem.

[0081] like Figure 4 As shown, in one embodiment of the present application, another method for automatically restoring a call stack is provided, the steps of the method comprising:

[0082] The client accesses the production server and obtains the web page data returned by the production server, and the client installs the front-end packaging tool plug-in;

[0083] Acquire error call stack information in the web page data based on the web page data returned by the production server and acquired by the client;

[0084] According to the call stack information of the error in the webpage data, the internal server of the client obtains the source code and the compiled code mapping relationship file information from the content distribution network according to the set storage strategy;

[0085] According to the source code and compiled code mapping relationship file obtained by the internal server, the internal server obtains the line and column numbers of the erroneous call stack and the source code position where the erroneous call stack parses the error;

[0086] The internal server obtains the row and column numbers of the erroneous call stack and the source code position where the erroneous call stack parses the error, and obtains an erroneous source code segment of the erroneous call stack.

[0087] It should be noted that Figure 4 It is an overall timing diagram of the automatic restoration of the call stack, which is only a surface data flow process. Its specific technical support depends on the various steps of the method for automatic restoration of the call stack provided in the embodiment of the present application.

[0088] It should be understood that although Figures 2 to 4The steps in the flowchart are shown in sequence as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be executed in other orders. Moreover, Figures 2 to 4 At least part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least part of the sub-steps or stages of other steps.

[0089] In one embodiment, Figure 5 As shown, a device 300 for automatically restoring a call stack is provided. The device 300 uses a front-end packaging tool plug-in to store the source code and compiled code mapping relationship file according to the strategy. When an erroneous call stack is obtained, the source code and compiled code mapping relationship file is used for decompilation to obtain the source code fragment of the erroneous call stack. The device 300 includes: a plug-in acquisition module, a storage control module, and a call stack restoration module.

[0090] The plug-in acquisition module is used to obtain the installation information of the front-end packaging tool plug-in and the configured trigger environment variable information;

[0091] A storage control module, used to obtain the information of the front-end packaging tool plug-in completing configuration according to the installation information of the front-end packaging tool plug-in and the configured trigger environment variable information; and to obtain the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in according to the information of the front-end packaging tool plug-in completing configuration and the source code;

[0092] The call stack restoration module is used to obtain the wrong call stack according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, and decompile the source code and compiled code mapping relationship file to obtain the source code fragment of the wrong call stack.

[0093] Specifically, in another embodiment of the present application, the storage control module is used to obtain information that triggers the startup of the front-end packaging tool plug-in; based on the information that triggers the startup of the front-end packaging tool plug-in, obtain information that the developer tool of the front-end packaging tool plug-in is set to only hide the source code mode; based on the developer tool of the front-end packaging tool plug-in being set to only hide the source code mode information, obtain the address information of the source file in the source code and compiled code mapping relationship file of the front-end packaging tool plug-in that does not contain the source code and compiled code mapping relationship file; based on the information that triggers the startup of the front-end packaging tool plug-in, obtain information that the front-end packaging tool plug-in introduces external plug-in and starts working.

[0094] Specifically, in another embodiment of the present application, the storage control module is used to obtain the configuration information of the front-end packaging tool plug-in; based on the configuration information of the front-end packaging tool plug-in, obtain the error call stack capture software development tool kit; based on the error call stack capture software development tool kit, obtain the source code and compiled code mapping relationship file upload information; based on the source code and compiled code mapping relationship file upload information, obtain the upload class initialization information of the simple storage service; based on the upload class initialization information of the simple storage service, obtain the operation security environment check information of the front-end packaging tool plug-in; based on the operation security environment check information of the front-end packaging tool plug-in, obtain the The front-end packaging tool plug-in successfully responds to the hook information of the construction; according to the front-end packaging tool plug-in successfully responds to the hook information, obtains the file path list information of the source code and compiled code mapping relationship file; according to the file path list information of the source code and compiled code mapping relationship file, obtains the uploaded source code and compiled code mapping relationship file and the corresponding JavaScript file with the same name; according to the uploaded source code and compiled code mapping relationship file and the corresponding JavaScript file with the same name, obtains the source code and compiled code mapping relationship file uploaded according to the set directory rule, and the source code is automatically injected by the error call stack capture software development kit.

[0095] Specifically, in another embodiment of the present application, the storage control module is used to obtain the publishing pipeline in the local development environment based on the information of the configuration completed by the front-end packaging tool plug-in; based on the publishing pipeline in the local development environment, obtain the packaging and processing of data by the production pipeline through the front-end packaging tool plug-in; based on the packaging and processing results of data by the production pipeline through the front-end packaging tool plug-in, obtain the production pipeline to deploy an online program package to the production server, and upload the source code and compiled code mapping relationship file to the internal server of this end; deploy the online program package to the production server based on the production pipeline, and upload the source code and compiled code mapping relationship file to the internal server of this end, and the internal server stores the source code and compiled code mapping relationship file to the content distribution network server.

[0096] Specifically, in another embodiment of the present application, the call stack restoration module is used to obtain an erroneous call stack in the source code and compiled code mapping relationship file according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in; obtain the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in according to the erroneous call stack in the source code and compiled code mapping relationship file; obtain a code snippet of the source file of the erroneous call stack according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in; and decompile the source code and compiled code mapping relationship file to obtain source code information when obtaining the call stack according to the code snippet of the source file of the erroneous call stack.

[0097] Specifically, in another embodiment of the present application, the call stack restoration module is used to obtain erroneous call stack information and interface verification information; based on the erroneous call stack information and interface verification information, obtain the line number, column number, source file name and content of the erroneous call stack; based on the line number, column number, source file name and content, and interface verification information of the erroneous call stack, obtain the storage strategy of the front-end packaging tool plug-in to download the source code and compiled code mapping relationship file corresponding to the erroneous call stack; according to the storage strategy of the front-end packaging tool plug-in, download the source code and compiled code mapping relationship file corresponding to the erroneous call stack, and obtain the source file corresponding to the erroneous call stack; based on the source file corresponding to the erroneous call stack, obtain the code snippet of the source file of the erroneous call stack.

[0098] According to the solution of automatic call stack restoration of the present invention, the installation information and configuration trigger environment variable information of the front-end packaging tool plug-in are obtained through the plug-in acquisition module; the configuration information of the front-end packaging tool plug-in is obtained through the storage control module according to the installation information and configuration trigger environment variable information of the front-end packaging tool plug-in; according to the configuration information and source code of the front-end packaging tool plug-in, the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in is obtained; the wrong call stack is obtained through the call stack restoration module according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, and the source code fragment of the wrong call stack is obtained by decompiling the source code and compiled code mapping relationship file. The present application can automatically decode the wrong call stack, so that the developer does not need to care about the wrong call stack decoding process, does not need to manage the SourceMap file, only needs to configure once, there is no possibility of exposing the source code, and there is no compatibility problem.

[0099] It should be understood that in order to streamline the present disclosure and aid in understanding one or more of the various inventive aspects, in the above description of exemplary embodiments of the present invention, various features of the present invention are sometimes grouped together into a single embodiment, figure, or description thereof. However, this disclosed method should not be interpreted as reflecting the following intention: that the claimed invention requires more features than those explicitly recited in each claim. More specifically, as reflected in the claims below, inventive aspects lie in less than all the features of the individual embodiments disclosed above. Therefore, the claims that follow the specific embodiment are hereby expressly incorporated into the specific embodiment, with each claim itself serving as a separate embodiment of the present invention.

[0100] Those skilled in the art will appreciate that the modules or units or components of the devices in the examples disclosed herein may be arranged in the devices described in the embodiment, or alternatively may be located in one or more devices different from the devices in the examples. The modules in the foregoing examples may be combined into one module or may be divided into multiple submodules.

[0101] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and in addition they may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive, all features disclosed in this specification (including the accompanying claims, abstracts and drawings) and all processes or units of any method or device disclosed in this manner may be combined in any combination. Unless otherwise expressly stated, each feature disclosed in this specification (including the accompanying claims, abstracts and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.

[0102] In addition, those skilled in the art will appreciate that, although some embodiments described herein include certain features included in other embodiments but not other features, the combination of features of different embodiments is meant to be within the scope of the present invention and form different embodiments. For example, in the claims below, any one of the claimed embodiments may be used in any combination.

[0103] In addition, some of the embodiments are described herein as methods or combinations of method elements that can be implemented by a processor of a computer system or by other devices that perform the functions. Therefore, a processor with necessary instructions for implementing the method or method elements forms a device for implementing the method or method elements. In addition, the elements described herein of the device embodiments are examples of devices for implementing the functions performed by the elements for the purpose of implementing the invention.

[0104] As used herein, unless otherwise specified, the use of ordinal numbers "first," "second," "third," etc. to describe common objects merely indicates that different instances of similar objects are involved, and is not intended to imply that the objects so described must have a given order in time, space, order, or in any other manner.

[0105] Although the present invention has been described according to a limited number of embodiments, it will be apparent to those skilled in the art, with the benefit of the above description, that other embodiments may be envisioned within the scope of the invention thus described. In addition, it should be noted that the language used in this specification is selected primarily for readability and teaching purposes, rather than for explaining or defining the subject matter of the present invention. Therefore, many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the appended claims. The disclosure of the present invention is illustrative, not restrictive, with respect to the scope of the present invention, which is defined by the appended claims.

Claims

1. A method for automatically restoring a call stack, the method uses a front-end packaging tool plug-in, stores the source code and compiled code mapping relationship file according to the strategy, decompiles the source code and compiled code mapping relationship file when obtaining an erroneous call stack, and obtains the source code fragment of the erroneous call stack, the method comprising the steps of: Get the installation information of the front-end packaging tool plug-in and the configured trigger environment variable information; According to the installation information of the front-end packaging tool plug-in and the configured trigger environment variable information, obtain the information that the front-end packaging tool plug-in completes the configuration, including obtaining the information that the front-end packaging tool plug-in triggers and starts, according to the information that the front-end packaging tool plug-in triggers and starts, obtain the developer tool of the front-end packaging tool plug-in is set to hide only the source code mode information, according to the developer tool of the front-end packaging tool plug-in is set to hide only the source code mode information, obtain the source file in the source code and compiled code mapping relationship file of the front-end packaging tool plug-in does not contain the address information of the source code and compiled code mapping relationship file, according to the information that the front-end packaging tool plug-in triggers and starts, obtain the information that the front-end packaging tool plug-in introduces an external plug-in and starts working; According to the configuration information and source code of the front-end packaging tool plug-in, a storage strategy for the source code and compiled code mapping relationship file of the front-end packaging tool plug-in is obtained; According to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, an erroneous call stack is obtained, and the source code fragment of the erroneous call stack is obtained by decompiling the source code and compiled code mapping relationship file, including obtaining the erroneous call stack in the source code and compiled code mapping relationship file according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, obtaining the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, obtaining the code fragment of the source file of the erroneous call stack according to the code fragment of the source file of the erroneous call stack, and decompiling the source code and compiled code mapping relationship file to obtain source code information when obtaining the call stack.

2. The method of claim 1, wherein: The steps of introducing external plug-in information and starting to work of the front-end packaging tool plug-in include: Obtain the front-end packaging tool plug-in to complete the configuration information; Complete the configuration information according to the front-end packaging tool plug-in, and obtain the wrong call stack to capture the software development toolkit; Capturing a software development kit according to the erroneous call stack, and obtaining the file upload information of the mapping relationship between the source code and the compiled code; According to the source code and compiled code mapping relationship file upload information, obtain the upload class initialization information of the simple storage service; According to the upload class initialization information of the simple storage service, the operation security environment check information of the front-end packaging tool plug-in is obtained; According to the operation security environment check information of the front-end packaging tool plug-in, the construction success response hook information of the front-end packaging tool plug-in is obtained; According to the successful response hook information of the front-end packaging tool plug-in, the file path list information of the source code and compiled code mapping relationship file is obtained; According to the file path list information of the source code and compiled code mapping relationship file, the uploaded source code and compiled code mapping relationship file and the corresponding JavaScript file with the same name are obtained; According to the uploaded source code and compiled code mapping relationship file and the corresponding JavaScript file with the same name, the source code and compiled code mapping relationship file uploaded according to the set directory rules are obtained, and the software development kit automatically injects the source code by capturing the erroneous call stack.

3. The method of claim 1, wherein: The step of obtaining the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in according to the configuration information and source code of the front-end packaging tool plug-in includes: According to the information of completing the configuration of the front-end packaging tool plug-in, obtain the release pipeline in the local development environment; According to the release pipeline in the local development environment, the production pipeline is obtained to package the data through the front-end packaging tool plug-in; According to the result of data packaging processing by the production line through the front-end packaging tool plug-in, the production line deploys an online program package to the production server, and uploads the source code and compiled code mapping relationship file to the internal server of the local end; The online program package is deployed to the production service end according to the production pipeline, and the source code and compiled code mapping relationship file is uploaded to the internal server of the local end, and the internal server stores the source code and compiled code mapping relationship file to the content distribution network server.

4. The method of claim 1, wherein: The step of obtaining the code snippet of the source file of the erroneous call stack according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in comprises: Get the error call stack information and interface verification information; Obtain the line number, column number, source file name and content of the erroneous call stack according to the erroneous call stack information and interface verification information; According to the line number, column number, source file name and content of the erroneous call stack, and interface verification information, the storage strategy of the front-end packaging tool plug-in is obtained to download the source code and compiled code mapping relationship file corresponding to the erroneous call stack; Download the source code and compiled code mapping relationship file corresponding to the erroneous call stack according to the storage strategy of the front-end packaging tool plug-in, and obtain the source file corresponding to the erroneous call stack; According to the source file corresponding to the erroneous call stack, a code snippet of the source file of the erroneous call stack is obtained.

5. A device for automatically restoring a call stack, wherein the device uses a front-end packaging tool plug-in to store the source code and compiled code mapping relationship file according to the strategy, and when obtaining an erroneous call stack, decompiles the source code and compiled code mapping relationship file to obtain a source code fragment of the erroneous call stack, and the device comprises: The plug-in acquisition module is used to obtain the installation information of the front-end packaging tool plug-in and the configured trigger environment variable information; A storage control module, configured to obtain information on the completion of configuration of the front-end packaging tool plug-in according to the installation information of the front-end packaging tool plug-in and the configured trigger environment variable information, including obtaining information on triggering and starting the front-end packaging tool plug-in, obtaining information on setting the developer tool of the front-end packaging tool plug-in to hide only the source code mode according to the information on triggering and starting the front-end packaging tool plug-in, obtaining address information that a source file in a source code and compiled code mapping relationship file of the front-end packaging tool plug-in does not contain the source code and compiled code mapping relationship file according to the information on triggering and starting the front-end packaging tool plug-in, and obtaining information on introducing an external plug-in by the front-end packaging tool plug-in and starting work; According to the configuration information and source code of the front-end packaging tool plug-in, a storage strategy for the source code and compiled code mapping relationship file of the front-end packaging tool plug-in is obtained; A call stack restoration module is used to obtain an erroneous call stack according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, and decompile the source code and compiled code mapping relationship file to obtain the source code fragment of the erroneous call stack, including obtaining the erroneous call stack in the source code and compiled code mapping relationship file according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, obtaining the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, obtaining the code fragment of the source file of the erroneous call stack according to the storage strategy of the source code and compiled code mapping relationship file of the front-end packaging tool plug-in, and decompiling the source code and compiled code mapping relationship file to obtain source code information when obtaining the call stack.

6. An electronic device comprising: one or more processors; and Memory; One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for executing any one of the methods according to claims 1-4.

7. A computer-readable storage medium storing one or more programs, wherein the one or more programs include instructions, and when the instructions are executed by a computing device, the computing device performs any one of the methods according to claims 1-4.

Images