GH-360: I removed the code in tidy-warnings

[jgallagher59701]

There was some old python code that was used to edit source files and a LLM (i.e., agentic AI) could use it in ways that pose a security threat. It was no longer used, so I removed it.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 0426ae42-e38a-43dc-a499-cb5c87038cfb

📥 Commits

Reviewing files that changed from the base of the PR and between b15a4d0 and 2f03c7c.

📒 Files selected for processing (5)

• tidy-warnings/README.md
• tidy-warnings/apply_overrides.py
• tidy-warnings/extract-warnings.py
• tidy-warnings/remove_redundant_virtual.py
• tidy-warnings/warnings_1.txt

💤 Files with no reviewable changes (5)

• tidy-warnings/README.md
• tidy-warnings/extract-warnings.py
• tidy-warnings/warnings_1.txt
• tidy-warnings/remove_redundant_virtual.py
• tidy-warnings/apply_overrides.py

---

📝 Walkthrough

• Removed unused tidy-warnings Python scripts and documentation.
• Removed stale warning entries.

Author	Lines added	Lines removed
James Gallagher	0	482

Walkthrough

The pull request removes the tidy-warnings documentation and three Python warning-fixing utilities, and deletes obsolete warning entries from warnings_1.txt.

Changes

Tidy-warnings removal

Layer / File(s)	Summary
Remove warning-fixing utilities and documentation tidy-warnings/README.md, tidy-warnings/apply_overrides.py, tidy-warnings/extract-warnings.py, tidy-warnings/remove_redundant_virtual.py	The documentation and scripts for extracting warnings, adding override, and removing redundant virtual keywords were deleted.
Remove obsolete warning data tidy-warnings/warnings_1.txt	Warning entries for methods in libdap4/Structure.h and libdap4/Sequence.h were removed.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related issues

• Python code in the tidy-warnings dir is a security issue #360 — Requests removal of the obsolete, security-flagged tidy-warnings scripts and related warning data.

Poem

A bunny found scripts in a dusty burrow,
And cleared old warnings without any sorrow.
The tools hopped away, the logs disappeared,
No redundant keywords remained to be feared.
“Clean code!” cried the rabbit, ears held high.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: removing the tidy-warnings code.
Description check	✅ Passed	The description is directly related to the change and explains why the unused code was removed.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jhrg/gh-360-sscan-issue

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[jgallagher59701]

No issues remain.