Updating a code file

Patent metadata

Field	Value
Publication number	US-11294661-B2
Application number	US-201715496813-A
Country	US
Kind code	B2
Filing date	Apr 25, 2017
Priority date	Apr 25, 2017
Publication date	Apr 5, 2022
Grant date	Apr 5, 2022

Abstract

Methods and systems for updating a file using heuristics. One system includes an electronic processor configured to identify a code file stored on a storage device and determine a signature of the code file. The electronic processor is also configured to compare the signature of the code file to each of a plurality of signatures to determine a degree of similarity between the signature of the code file and each of the plurality of signatures, wherein each of the plurality of signatures is associated with a code update, and, in response to the degree of similarity between the signature of the code file and one of the plurality of signatures satisfying a predetermined threshold, apply the code update associated with the one of the plurality of signatures to the code file.

First claim

What is claimed is:

1. A system for updating a code file, the system comprising:
an electronic processor configured to
identify the code file stored on a storage device,
parse the code file into a plurality of subsections,
determine a signature for each of the plurality of subsections,
compare the signature for each of the plurality of subsections to each of a plurality of predetermined signatures to determine a degree of similarity between the signature for each of the plurality of subsections and each of the plurality of predetermined signatures, each of the plurality of predetermined signatures associated with a code update fixing a known issue with an associated code file, and
in response to the degree of similarity between the signature for one of the plurality of subsections and one of the plurality of known signatures satisfying a predetermined threshold, apply the code update associated with the one of the plurality of known signatures to the one of the plurality of subsections included in the code file, wherein applying the code update includes adding a comment to the one of the plurality of subsections, the comment including at least one edited instruction based on the code update.

2. The system of claim 1 , wherein the electronic processor is configured to identify the code file stored on the storage device in response to use of the code file.

3. The system of claim 1 , wherein the electronic processor is configured to identify the code file stored on the storage device as part of a scan of the storage device on a predetermined frequency.

4. The system of claim 1 , wherein the electronic processor is further configured to store a record of the code file, the record including the signature of the code file and a storage location of the code file.

5. The system of claim 1 , wherein the electronic processor is configured to apply the code update associated with the one of the plurality of signatures to the code file by automatically editing at least one instruction included in the code file based on the code update.

6. The system of claim 1 , wherein the electronic processor is configured to apply the code update associated with the one of the plurality of signatures to the code file by prompting a user to approve application of the code update to the code file and automatically applying the code update to the code file in response to receiving approval from the user.

7. A method of updating a file, the method comprising:
receiving a plurality of file updates and a plurality of signatures from at least one user device, each of the plurality of file updates associated with at least one of the plurality of signatures;
identifying a file stored on a storage device;
determining a signature of the file;
comparing the signature of the file to each of the plurality of signatures to determine a degree of similarity between the signature of the file and each of the plurality of signatures;
in response to the degree of similarity between the signature of the file and one of the plurality of signatures satisfying a first predetermined threshold, determining a confidence score of one of the plurality of updates associated with the one of the plurality of signatures, wherein the confidence score indicates a likelihood that the one of the plurality of updates will be successful; and
in response to the confidence score satisfying a second predetermined threshold, automatically, with an electronic processor, applying the one of the plurality of updates associated with the one of the plurality of signatures to the file, wherein applying the one of the plurality of updates includes adding a comment to the file, the comment including at least one edited instruction based on the code update.

8. The method of claim 7 , further comprising receiving feedback after applying the one of the plurality of code updates to the file and automatically updating the confidence score based on the feedback.

9. The method of claim 8 , wherein receiving the feedback includes receiving telemetry data tracking a manual edit to the file.

10. The method of claim 8 , wherein receiving the feedback includes receiving an error log for the file.

11. The method of claim 7 , further comprising verifying the one of the plurality of updates applied to the file by executing an original version of the file before applying the one of the plurality of updates to the file to generate an original set of results, executing an updated version of the file after applying the one of the plurality of updates to the file to generate an updated set of results, and comparing the original set of results and the updated set of results and automatically updating the confidence score based on the comparing of the original set of results and the updated set of results.

12. The method of claim 7 , wherein receiving the plurality of file updates from at least one user device includes receiving a first subset of the plurality of file updates from a first set of user devices associated with an organization and receiving a second subset of the plurality of files updates from a second set of user devices outside of the organization.

13. The method of claim 7 , wherein comparing the signature of the file to each of the plurality of signatures to determine a degree of similarity between the signature of the file and each of the plurality of signatures includes assigning a weight to each of the plurality of signatures, wherein the weight represents a degree of similarity between the signature of the file and each of the plurality of signatures, and further comprising identifying a subset of the plurality of signatures having a weight satisfying the first predetermined threshold.

14. A non-transitory, computer-readable medium including instructions that, when executed by an electronic processor, cause the electronic processor to execute a set of functions, the set of functions comprising:
scanning at least one storage device to identify a plurality of code files;
determining a type of update for each of the plurality of code files based on a signature of each of the plurality of code files, the type of update including at least one selected from a group consisting of an automatic update, an automatic update with manual review, and a manual update;
determining a confidence score for each of the plurality of code files where the type of the update includes an automatic update, wherein the confidence score indicates a likelihood that the type of update will be successful;
generating a user interface, the user interface listing the plurality of code files, the type of update for each of the plurality of code files, the confidence score for each of the plurality of code files where the type of the update includes an automatic update, and at least one selection mechanism for deploying a software product update;
displaying the user interface on a user device; and
in response to receiving input from a user through the at least one selection mechanism, deploying the software product update, wherein deploying the software product update includes updating one or more instructions included in each of the plurality of code files.

15. The non-transitory, computer-readable medium of claim 14 , wherein the user interface further includes at least one readiness score for the plurality of code files, the readiness score specifying a percentage of the plurality of code files needing updating prior to deployment of a software product update.

16. The non-transitory, computer-readable medium of claim 14 , wherein the set of functions further includes receiving input from a user th

Assignees

• Microsoft Technology Licensing Llc

Inventors

• Doyle Darren
• Farrell Terry
• Doyle Thomas

Classifications

• G06F8/658 Primary

  Incremental updates; Differential updates · CPC title