ngducloc1112002/satd-repayment-context

SATD Repayment Context Dataset

Extends the SATD Repayment replication package (Python: 58,722 rows, Java: 97,347 rows) with per-SATD repository context, all anchored at parent(deleted_in_commit) (the commit right before the fix), so no information from the repayment itself leaks into the context. Total package size: ~1.56 GB.

Contents

data/
  python_final.parquet     -- main SATD table (Python), 58,722 rows, 130 MB
  java_final.parquet       -- main SATD table (Java), 97,347 rows, 114 MB
  python_context.jsonl.gz  -- 1 JSON object/line, aligned by row_index, 310 MB
  java_context.jsonl.gz    -- 1 JSON object/line, aligned by row_index, 1045 MB
code/
  *.py, *.sh               -- extraction pipeline (clone, snapshot, extractors, driver)

Join *_context.jsonl.gz to *_final.parquet on row_index == the parquet row's positional index (0-based, matches df.reset_index().index).

Main table statistics

	Python	Java
Rows	58,722	97,347
train / test / dev	50,075 / 5,745 / 2,902	83,211 / 9,013 / 5,123
Unique repos	7,219	5,181
Avg SATD/repo	8.1	18.8
Method tokens before (mean / median)	238 / 180	175 / 112
Method tokens after (mean / median)	236 / 175	183 / 119
containing_method_applied_approach	WITH_AST: 50,886 (86.7%), WITHOUT_AST: 7,836 (13.3%)	AST_FALLBACK: 97,347 (100.0%)
created_at_date range	1970-01-16 to 2024-03-09	1997-06-03 to 2024-05-04
deleted_at_date range	1999-01-15 to 2024-03-15	1997-06-13 to 2024-05-06

Top 5 repos by SATD count

Python	Java
facebook/Ax (837)	col-e/r8 (694)
mozillazg/pypy (503)	aokp/frameworks_base (685)
Checkmk/checkmk (480)	ultimate-pa/ultimate (657)
openstack/nova (439)	evolveum/midpoint (564)
getsentry/sentry (367)	bazelbuild/bazel (498)

Note: a handful of created_at_date/deleted_at_date values fall in 1970/1997, inherited as-is from the upstream replication package's git metadata (likely corrupted author-date fields in the source repos, not introduced by this pipeline).

Context extraction status

Python (58,722 rows):

Status	Count	%
ok	56,632	96.4%
clone_failed	1,581	2.7%
file_not_found_at_snapshot	468	0.8%
commit_not_found	41	0.1%

Java (97,347 rows):

Status	Count	%
ok	83,177	85.4%
clone_failed	13,246	13.6%
file_not_found_at_snapshot	847	0.9%
commit_not_found	77	0.1%

clone_failed = source repo deleted/renamed/made private since the original SATD Tracker crawl; commit_not_found = the pre-repayment commit isn't reachable in the cloned history; pending = extraction still running when this package was built.

Context field coverage (within status: "ok" rows)

Python (56,632 ok rows):

Field	Rows with data	%
local_code_window	56,632	100.0%
commit_history	56,632	100.0%
directory_tree_size	56,632	100.0%
imports_used	56,349	99.5%
documentation_files	52,820	93.3%
callees	50,854	89.8%
dependency_manifests	49,851	88.0%
class_hierarchy	46,224	81.6%
prior_fix_commits	40,226	71.0%
related_test_files	31,209	55.1%
ci_workflow_files	30,962	54.7%
coding_convention_findings	19,678	34.7%
callers	18,498	32.7%
related_issues	0	0.0%

Java (83,177 ok rows):

Field	Rows with data	%
local_code_window	83,177	100.0%
class_hierarchy	83,177	100.0%
commit_history	83,177	100.0%
directory_tree_size	83,177	100.0%
imports_used	82,675	99.4%
dependency_manifests	62,653	75.3%
documentation_files	61,544	74.0%
callees	60,138	72.3%
prior_fix_commits	43,152	51.9%
ci_workflow_files	24,873	29.9%
callers	22,854	27.5%
related_test_files	21,176	25.5%
related_issues	0	0.0%
coding_convention_findings	0	0.0%

Coverage gaps are expected, not bugs: related_issues requires a GITHUB_TOKEN (unset for this run, always null); ci_workflow_files/related_test_files/ dependency_manifests/documentation_files are only populated if the repo actually has a matching file at that snapshot; callers is low because it only matches same-file call sites (a heuristic, not a full cross-module call graph).

Context fields (per row)

Field	Description
status	ok, clone_failed, commit_not_found, file_not_found_at_snapshot, or pending
snapshot_commit	the anchor commit (parent(deleted_in_commit)) everything below is read at
local_code_window	+-10 lines of code around the SATD
class_hierarchy	classes/interfaces declared in the file, with bases
enclosing_function / callers / callees	function containing the SATD and its direct call relationships (same-file heuristic)
imports_used	modules imported by the file
directory_tree_size	file count in the repo at that snapshot
dependency_manifests	contents of requirements.txt/pom.xml/etc. found in the repo
documentation_files	README/ADR/OpenAPI files found (truncated to 2000 chars)
ci_workflow_files	CI config files found (GitHub Actions/Travis/Jenkins/CircleCI)
related_test_files	candidate test file paths (naming-convention match)
commit_history / prior_fix_commits	git log up to the snapshot, and the subset whose message mentions fix/bug
related_issues	GitHub issues before the SATD was resolved -- null unless a GITHUB_TOKEN was configured during extraction
coding_convention_findings	pyflakes findings (Python only)
parse_backend	ast (Python 3) or parso (Python-2-syntax fallback for historical files); Java always uses javalang

Known limitations

• related_issues requires a GITHUB_TOKEN (not configured for this run) -- always null.
• callers/callees are same-file heuristics (direct Name(...)/obj.attr(...) calls), not a full cross-module call graph -- a function called only from another file won't show up as a caller.
• No build/compile/test-execution was performed anywhere in this pipeline -- everything is static analysis or plain git reads, so no third-party code was ever executed.
• Python files with Python-2-only syntax (print statement, except X, e:, octal literals) are parsed via a parso (0.7.1, last release bundling the 2.7 grammar) fallback when ast fails; parse_backend marks which path was used for each row.

Provenance

Derived from the SATD Repayment replication package (ReplicationPackage-SATD-Repayment-Datasets), df3_train + df3_test + df3_dev per language, filtered to is_repayment_llama3 == "yes". Context was extracted by cloning each repo (partial clone, --filter=blob:none) and reading file/tree/log state at parent(deleted_in_commit) via git show/git ls-tree/git log -- no build step, no test execution, no code from the target repos was ever run.