Skip to content
Topaz6.0 · Before release
Download

Search documentation

Specification 6.0 · Not released · Tested product 5.21.3

Use arrow keys to choose a result. Press Enter to open.

Type an API name, diagnostic number, rule, or project topic.

    Diagnostics

    TPZ3005: Physical path escapes root

    A module resolves through a physical path or symlink outside the module root.

    Diagnostic and cause

    Link

    Physical path escapes root

    Family
    topaz
    Phase
    resolve
    Code
    TPZ3005

    Cause and conditions

    An imported source whose canonical physical path lies outside the selected root is rejected with TPZ3005 before its source is loaded.

    Related rule: Trigger and repair

    Response

    Place the source inside the root or choose a root that contains its physical location. Check symbolic-link targets as well as import spellings.

    Source evidence

    Compiler phase: resolve.

    Compiler explanation: A module resolves through a physical path or symlink outside the module root.

    Message templates. The marker ⟨value⟩ stands for text computed for the reported program.

    • the entry ⟨value⟩ resolves outside the root (symlink/alias containment) Source
    • ⟨value⟩ resolves outside the root (symlink/alias containment) Source

    The imported path crosses a symbolic link to a physical source outside the selected root. Textual containment of the import path does not admit the target.

    Rulediagnostics.tpz3005.rule

    Trigger and repair

    An imported source whose canonical physical path lies outside the selected root is rejected with TPZ3005 before its source is loaded.

    Examples Product diagnostic testCorrected program

    Diagnostics TPZ3005

    Source evidence

    Response

    Link

    Place the source inside the root or choose a root that contains its physical location. Check symbolic-link targets as well as import spellings.

    Reproduction and verification

    Link

    Product diagnostic test

    Link

    Syntax fragment

    root/example.tpzProduct diagnostic testOpen in Playground
    1. import lib
    target product 5.21.3
    outside/lib.tpzProduct diagnostic testOpen in Playground
    1. export let value = 1
    Expected result

    Expected result

    The separate diagnostic product test validates this command, runtime diagnostic, or filesystem setup. The shared example runner does not execute that assertion plan.

    Prepare the files shown above, then complete this setup.

    Create the symbolic link root/lib.tpz with target ../outside/lib.tpz. Keep the link and its target within the same temporary test directory.

    Run topaz check root/example.tpz --language-version 5.21 --root root.

    Expect exit status 1, empty standard output, and TPZ3005.

    The imported path crosses a symbolic link to a physical source outside the selected root. Textual containment of the import path does not admit the target.

    The primary location is root/example.tpz:1:8.

    Expect exactly one diagnostic.

    The diagnostic product test checks these expectations with the same files and command.

    Source evidence

    Corrected program

    Link

    check · checking · Verification: not-run

    root/example.tpzCorrected programOpen in Playground
    1. import lib
    Expected outputexit 0
    $ topaz check root/example.tpz --root root · target product 5.21.3
    root/lib.tpzCorrected programOpen in Playground
    1. export let value = 1
    Expected result

    Expected result

    Checking accepts the program. Exit code 0.

    No stderr.

    This exact example has not been executed.

    This program applies the repair described above. The verification status records whether it has been run.

    Source evidence

    Menu

    Download