Skip to content

Data-audit methods: Presidio documentation URL embedded in error messages (outdated) (TECH-T06-004) #491

Closed

Description

@cemililik

Wave 2 · theme D2-7: Next-release technology updates · highest severity Next release · 1 finding(s) · effort not estimated

Summary

The actionable hint in two ValueError messages leads to a 404. The repository link in data_audit.md:405 still resolves through a redirect.

Primary finding

TECH-T06-004 — Data-audit methods: Presidio documentation URL embedded in error messages (outdated)

severity Next release

Item. Presidio documentation URL embedded in error messages · verdict: outdated · urgency: Next release

State in ForgeLM. forgelm/data_audit/_pii_ml.py:109 and :178 point operators to https://microsoft.github.io/presidio/analyzer/languages/. docs/guides/data_audit.md:405 links github.com/microsoft/presidio.

State of the ecosystem on 2026-10-01. On 2026-10-01 the old URL returned HTTP 404 (arbiter re-fetch), and https://presidio.dataprivacystack.org/analyzer/languages/ returned 200. The GitHub repository is now data-privacy-stack/presidio.

Impact. The actionable hint in two ValueError messages leads to a 404. The repository link in data_audit.md:405 still resolves through a redirect.

Recommendation. Change both URLs to https://presidio.dataprivacystack.org/analyzer/languages/ and update the repository link.

Sources.

Acceptance criteria

  • Each statement is re-checked against the code at fix time.
  • Documentation listed above is corrected in English and in its Turkish mirror in the same PR.
  • Every finding in this issue is resolved or explicitly closed with a reason.

Found by the October 2026 ForgeLM code and documentation review against commit cab2947. Code links point at that commit; line numbers may have moved since. Finding IDs (CR-…, DOC-…, TECH-…) are stable references for this backlog.

Activity

  1. added
    dependenciesDependency or ecosystem currency
    source: review-2026-10Found by the October 2026 code and documentation review
    urgency: next-releaseTechnology currency: fix in the next release
    wave: 2Roadmap wave 2: high severity, larger effort; next-release tech
    on Oct 9, 2026
  2. cemililik commented on Oct 11, 2026

    @cemililik
    CollaboratorAuthor

    Where to start

    Thanks for taking a look. Please confirm the issue is unassigned and comment before starting so work does not overlap.

    Start with these files on development:

    Replace the dead language-help URL in both actionable error paths with https://presidio.dataprivacystack.org/analyzer/languages/ and update related guide links. Exercise unsupported-language and unsupported-analyzer errors with mocks, asserting the exception remains actionable and points to the current documentation. Tests must not fetch the URL or install spaCy models.

    Old help URL returned 404; the current primary documentation returned 200. Static source evidence plus HTTP check, not an ML-model execution.

    Run the focused tests:

    pytest tests/test_data_audit.py --no-cov

    Run these guards/checks as applicable to the changed files:

    ruff format --check forgelm/data_audit/_pii_ml.py tests/test_data_audit.py
    ruff check forgelm/data_audit/_pii_ml.py tests/test_data_audit.py
    python3 tools/check_bilingual_parity.py --strict
    python3 tools/check_bilingual_code_blocks.py --strict
    python3 tools/check_anchor_resolution.py --strict
    python3 tools/check_tr_links_prefer_mirror.py --strict
    python3 tools/check_usermanual_self_contained.py --strict
    python3 tools/check_usermanual_schema_drift.py --strict

    If user-facing documentation changes, update the existing Turkish mirror in the same PR; keep commands, code and terminal output in English and structurally aligned. English-only contributor standards need no new mirror.

    Open the PR against development with Fixes #491 once every finding is resolved or explicitly closed with a reason; use Refs #491 for partial work and list the resolved finding IDs.

  3. added a commit that references this issue on Oct 14, 2026
    549a239
  4. added 2 commits that reference this issue on Oct 17, 2026
    175cdcb
    8436b69
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependenciesDependency or ecosystem currencygood first issueGood for newcomerssource: review-2026-10Found by the October 2026 code and documentation reviewurgency: next-releaseTechnology currency: fix in the next releasewave: 2Roadmap wave 2: high severity, larger effort; next-release tech

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions