Datasets:
Tasks:
Text Generation
Formats:
parquet
Languages:
English
Size:
10K - 100K
ArXiv:
Tags:
code
DOI:
License:
Update README.md
Browse files
README.md
CHANGED
|
@@ -430,13 +430,29 @@ configs:
|
|
| 430 |
This is the data for **Bug Localization** benchmark as part of LCA.
|
| 431 |
The bug localization problem can be formulated as follows: given an issue with a bug description and a repository snapshot in a state where the bug is reproducible, identify the files within the repository that need to be modified to address the reported bug.
|
| 432 |
|
| 433 |
-
The dataset provides all required components for evaluation of
|
| 434 |
* Bug issue description
|
| 435 |
* Repositories from which the content on the state of the commit SHA where the bug is reproducible can be extracted
|
| 436 |
* List of files that should be changed in order to solve the bug
|
| 437 |
* Other additional data and metrics, that can be useful in approach development
|
| 438 |
|
| 439 |
-
The collected dataset was carefully filtered, enhances with useful metrics and, what is more, manually labeled, which assures the data quality and provides a golden subset of good examples for evaluation
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 440 |
The following sections will describe the utilities around the dataset as well as detailed dataset content description.
|
| 441 |
|
| 442 |
## How-to
|
|
|
|
| 430 |
This is the data for **Bug Localization** benchmark as part of LCA.
|
| 431 |
The bug localization problem can be formulated as follows: given an issue with a bug description and a repository snapshot in a state where the bug is reproducible, identify the files within the repository that need to be modified to address the reported bug.
|
| 432 |
|
| 433 |
+
The dataset provides all required components for evaluation of bug localization approaches in real project-level large-scale data collected from GitHub, including:
|
| 434 |
* Bug issue description
|
| 435 |
* Repositories from which the content on the state of the commit SHA where the bug is reproducible can be extracted
|
| 436 |
* List of files that should be changed in order to solve the bug
|
| 437 |
* Other additional data and metrics, that can be useful in approach development
|
| 438 |
|
| 439 |
+
The collected dataset was carefully filtered, enhances with useful metrics and, what is more, manually labeled, which assures the data quality and provides a golden subset of good examples for evaluation.\
|
| 440 |
+
Moreover, the dataset was splitted into several categories, naming:
|
| 441 |
+
|
| 442 |
+
| **Category** | **Description** | **Number of data points** |
|
| 443 |
+
|:------------------:|:----------------------------------------:|:----------------------------------------:|
|
| 444 |
+
| `py` | Only `.py` files in changes | 4,339 |
|
| 445 |
+
| `java` | Only `.java` files in changes | 2,522 |
|
| 446 |
+
| 'kt' | Only `.kt` files in changes | 618 |
|
| 447 |
+
| 'mixed' | At list one `.java`, `.py`, or `.kt` file in changes with any other changed files | 2,322 |
|
| 448 |
+
|
| 449 |
+
And splits, naming:
|
| 450 |
+
| **Split** | **Description** |
|
| 451 |
+
|:------------------:|:----------------------------------------:|
|
| 452 |
+
| `dev` | All collected data point |
|
| 453 |
+
| `test` | Manually verified data point |
|
| 454 |
+
| `train` | Rest data point from `dev` except `test` |
|
| 455 |
+
|
| 456 |
The following sections will describe the utilities around the dataset as well as detailed dataset content description.
|
| 457 |
|
| 458 |
## How-to
|