Management of software bugs in a data processing system

Patent metadata

Field	Value
Publication number	US-10924362-B2
Application number	US-201815940740-A
Country	US
Kind code	B2
Filing date	Mar 29, 2018
Priority date	Jan 15, 2018
Publication date	Feb 16, 2021
Grant date	Feb 16, 2021

Abstract

Methods, systems and computer programs are disclosed for managing data bugs in a data processing system comprising one or more data resources. The method may comprise receiving an indication of one or more bugs relating to one or more data resources, and contextual information for the one or more bugs and determining, from the received indication, one or more bug types and grouping the bugs by bug type for the same data resource to produce a aggregated list of open issues requiring fixing. Further operations may comprise presenting the aggregated list of one or more open issues on a user interface for selection, the one or more open issues being selectable, and, responsive to receiving selection of a particular open issue, presenting contextual information for the one or more bugs within the group on the user interface.

First claim

The invention claimed is:

1. A method of managing software bugs in a data processing system comprising one or more data resources, the method being performed using one or more processors and comprising:
receiving an indication of one or more bugs relating to one or more data resources, and contextual information for the one or more bugs;
determining, from the received indication, one or more bug types and grouping the bugs by bug type for the same data resource to produce an aggregated list of open issues requiring fixing;
presenting the aggregated list of one or more open issues on a user interface for selection, the one or more open issues being selectable, each open issue comprising one or more bugs of a common bug type;
responsive to receiving selection of a particular open issue, presenting particular contextual information of the particular open issue, the particular contextual information comprising:
a description of any of patches, fixes, or updates associated with the particular open issue; and
a hash identifier referring to the one or more bugs of the particular open issue, that uniquely identifies the particular open issue and links the particular open issue to other issues on the user interface; and

providing an option to deploy a same fix to all data resources to which the bugs of the particular open issue are related, and wherein the presenting contextual information further comprises:
displaying a list of version numbers of the data resource affected by the particular open issue directly above a list of deployments affected by the particular open issue;
displaying the list of deployments affected by the particular open issue directly above the hash identifier of the particular open issue;
displaying the hash identifier of the particular open issue directly above a date or a time, or the description of any of patches, fixes, or updates associated with the particular open issue, and further comprising:
responsive to clicking a button or link on the user interface, presenting a description of a service, stack, type, log count, and a link to individual stack traces for each of the deployments.

2. The method of claim 1 , wherein, responsive to receiving selection of the particular open issue, the presented contextual information comprises an expanded list of individual bugs, grouped or ordered based on type of the contextual information.

3. The method of claim 1 , wherein, responsive to receiving selection of the particular open issue, the presented contextual information comprises one or more version numbers of the data resource to which the bug is related.

4. The method of claim 3 , wherein the contextual information further comprises one or more of a deployment identifier indicative of where the affected one or more data resources are running, a date and/or time indicative of when the bug occurred, and a user identifier indicative of one or more users operating the data resource at said date and/or time.

5. The method of claim 1 , further comprising generating a first unique identifier for each indicated bug, which unique identifier is decodable upon selection of a particular bug from an expanded list of individual bugs, to provide to the user interface contextual information for the particular bug.

6. The method of claim 1 , further comprising receiving a close bug instruction indicative that a particular bug within an open issue has been fixed, and responsive thereto, removing the particular bug from the open issue.

7. The method of claim 1 , further comprising receiving a close issue command indicative that all bugs within an open issue have been fixed, and responsive thereto, closing the open issue such that it becomes a closed issue and no longer appears on the list of open issues.

8. The method of claim 6 , further comprising re-opening a closed bug or a closed issue, responsive to a further bug being received relating to the same bug type.

9. The method of claim 7 , further comprising re-opening a closed bug or a closed issue, responsive to a further bug being received relating to the same bug type.

10. The method of claim 8 , wherein the re-opened bug or re-opened issue comprises contextual data for the re-opened bug or re-opened issue, including an indication of one or more fixes previously applied, and contextual data for the further bug.

11. The method of claim 10 , wherein the indication of the one or more fixes previously applied comprises a link or option to deploy the same fix to the identified data resource, the method further comprising deploying said same fix responsive to user selection thereof.

12. The method of claim 6 , wherein in the event that a particular bug or open issue relating to a particular data resource version is closed, the method further comprises automatically closing earlier open versions of bugs or issues relating to the same bug type.

13. The method of claim 7 , wherein in the event that a particular bug or open issue relating to a particular data resource version is closed, the method further comprises automatically closing earlier open versions of bugs or issues relating to the same bug type.

14. A non-transitory computer-readable storage medium including instructions that, when executed by at least one processor of a computing system, cause the computing system to perform a method comprising:
receiving an indication of one or more bugs relating to one or more data resources, and contextual information for the one or more bugs;
determining, from the received indication, one or more bug types and grouping the bugs by bug type for the same data resource to produce a aggregated list of open issues requiring fixing, each open issue comprising one or more bugs of a common bug type;
presenting the aggregated list of one or more open issues on a user interface for selection, the one or more open issues being selectable; and
responsive to receiving selection of a particular open issue, presenting particular contextual information of the particular open issue, the particular contextual information comprising:
a description of any of patches, fixes, or updates associated with the particular open issue;
a hash identifier referring to the one or more bugs of the particular open issue, that uniquely identifies the particular open issue and links the particular open issue to other issues on the user interface; and
providing an option to deploy a same fix to all the data resources to which the bugs of the particular open issue are related, and wherein the presenting contextual information further comprises:
displaying a list of version numbers of the data resource affected by the particular open issue directly above a list of deployments affected by the particular open issue;
displaying the list of deployments affected by the particular open issue directly above the hash identifier of the particular open issue;
displaying the hash identifier of the particular open issue directly above a date or a time, or the description of any of patches, fixes, or updates associated with the particular open issue; and
responsive to clicking a button or link on the user interface, presenting a description of a service, stack, type, log count, and a link to individual stack traces for each of the deployments.

15. The non-transitory computer-readable storage medium of claim 14 , wherein, responsive to receiving selection of the particular open issue, the presented contextual information comprises an expanded list of individual bugs, grouped or ordered based on type of the contextual information.

16. A system for managing software bugs in a data processing sy

Assignees

• Palantir Technologies Inc

Inventors

• Mallah Amr Al
• Abdelsalam Mahmoud
• Nazario Michael
• Wang Peter
• Lakshmanan Vivek

Classifications

• G06F11/3698

  Environments for analysis, debugging or testing of software · CPC title

• G06F11/366

  using diagnostics (G06F11/0703 takes precedence) · CPC title

• G06F11/0787

  Storage of error reports, e.g. persistent data storage, storage using memory protection · CPC title

• G06F11/0769

  Readable error formats, e.g. cross-platform generic formats, human understandable formats · CPC title

• G06F11/0751

  Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06) · CPC title