Skip to content

Spawn failures end with a misleading 'cannot infer a schema' error #1187

Closed

Description

@thekevinbot

When every file's parser fails to spawn (e.g. --on-file extract.py with the script not on $PATH), dirsql reports the spawn error per file and then ends with "parser produced no rows ... cannot infer a schema". The real cause is the spawn failure; the schema line points the user the wrong way.

Expected: when no file produced rows because every parser failed to spawn, the final error names the spawn failure, not schema inference.

Split out of #1172 because it changes behavior, not just wording.

Activity

  1. thekevinbot commented on Oct 2, 2026

    @thekevinbot
    CollaboratorAuthor

    Fixed by PR #1245 (the per-file loop removal): a parser that fails to spawn now fails the statement with the spawn error and no schema-inference line follows. Evidence in the PR body. Closes on merge.

  2. self-assigned this
    on Oct 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions