You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Spawn failures end with a misleading 'cannot infer a schema' error #1187
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.
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.
Activity
thekevinbot commentedon Oct 2, 2026
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.