dsh-compile-digest
Manifest validRead-only LaTeX build-log diagnostics for DeepSeek Harness, with source locations, context and duplicate grouping.
dsh-compile-digest
Parse LaTeX build logs into structured diagnostics for DeepSeek Harness.
The log_parse tool extracts recognised errors and warnings, keeps reported file positions and source context, and groups identical messages while retaining their distinct locations. It reads saved logs without running builds or modifying source files.
Installation
Requires Node.js 24.9 or later. Registry integration was checked with DSH tools 0.2.2-rc.3.
In DSH, open Plugins → Add plugin and paste:
https://github.com/DengyiGu/dsh-compile-digest
Or install a tagged version into a web profile:
dsh plugin --profile web add github:DengyiGu/dsh-compile-digest#v0.1.0
An installable .tgz is also available under Releases. The repository ships executable JavaScript and needs no compilation, install scripts or extra runtime dependencies. DSH supplies the host peers. Bare package-name installation requires a separate npm publication.
Usage
log_parse({
path: 'C:/work/paper/build.log',
toolchain: 'auto',
maxDiagnostics: 20,
includeBoxWarnings: false,
})
Use an absolute path where possible. Relative paths resolve against the DSH process working directory. Only the saved log is needed; TeX does not need to be installed to parse it.
| Parameter | Default | Meaning |
|---|---|---|
path | required | Log file to read |
toolchain | auto | auto or latex |
maxDiagnostics | 20 | Maximum displayed diagnostic groups |
includeBoxWarnings | false | Display overfull/underfull box warnings instead of only counting them |
For example, ask DSH: “Parse C:/work/paper/build.log, show the errors with their file positions, and keep repeated occurrences grouped.”
Example output from a real included-file error:
latex · recognized · 19 lines
1 error(s), 0 warning(s) · 1 unique, 1 occurrence(s) · showing 1
ERROR Undefined control sequence.
./chapters/one.tex:2 ctx: \badcommandhere
run: Output written on main.pdf (1 page, 14785 bytes).
TeX can write a PDF despite reporting errors. recognized describes the log format and completion markers; it does not mean the build was error-free.
Supported logs
pdflatex,xelatexandlualatex: classic console output,-file-line-erroroutput and transcript.logfiles.latexmkcaptures containing the supported engine output.- Real captures cover pdfTeX 1.40.28, XeTeX 0.999997, LuaHBTeX 1.22.0 and latexmk 4.87.
Typst and other compiler dialects are not supported in this release.
Results and configuration
Each diagnostic contains a severity, message, occurrence count, distinct locations and associated notes. Locations include a file, line, line range or source context only when available. TeX does not report columns, so the plugin leaves them absent. Error codes remain empty for this dialect.
Grouping uses severity and whitespace-normalised messages. Numbers, paths and punctuation are preserved. Errors precede warnings; order within each severity follows first appearance. Recognised summary messages become runNotes rather than duplicate diagnostics.
The result includes summary, runNotes and parseNotes. Summary counts cover all parsed diagnostics, even when the display cap hides groups. filteredBoxWarnings counts box warnings omitted by default. If the read limit is reached, all statistics describe only the prefix actually read.
parseStatus | Meaning |
|---|---|
recognized | Recognised TeX structure with an end-of-run marker |
partial | Recognised but incomplete input, including a final incomplete engine pass |
unrecognized | No supported structure; no conclusion about build success |
Plugin settings provide defaults for toolchain, maxDiagnostics and includeBoxWarnings. maxBytes defaults to 4000000 and limits bytes read from the start of a file. Calls respect cancellation.
Development and verification
npm test
npm run check
npm run verify
npm pack
Tests run offline with Node's built-in runner. Parser tests use captured and explicitly labelled synthetic fixtures; adapter tests substitute host imports. Fixture provenance records capture commands, versions and sanitisation.
Separate integration checks mounted the actual Cordis 4.1.0 and ToolsService 0.2.2-rc.3 with Schemastery 3.19.0, registered the packaged plugin, directly invoked log_parse, and validated its output schema. The system-prompt dependency used a minimal callback sink. Full DSH application startup and conversation-driven invocation remain unverified.
Limitations
File attribution follows TeX's file-open markers. Closed or ambiguous file contexts leave the location unspecified; wrapped file markers can be ambiguous. Multi-run boundaries are not exposed. Notes are compiler explanations, and message grouping does not establish a common root cause. The plugin does not execute commands, repair code or start background services.
License
MIT.
Comments
Loading…
Similar plugins
by Wanbinyu
Read-only, redacted provider error diagnostics for DeepSeek Harness
★ 3
MIT
TypeScript
Oct 14, 2026
dsh plugin --profile web add dsh-error-lensby xianfanwindy
Read-only Windows startup diagnostics for DeepSeek Harness.
★ 0
MIT
TypeScript
Aug 21, 2026
dsh plugin --profile web add dsh-doctor-windowsby builtin-pb
The single plugin you need for DSH — build, test, diagnose, and maintain DeepSeek Harness plugins and core.
★ 7
MIT
JavaScript
Sep 19, 2026
dsh plugin --profile web add dsh-developerby Liu-Bot24
DeepSeek Harness(DSH)只读执行轨迹复盘插件,支持规则分析、独立模型解读、证据定位、任务概览与运行对比。
★ 6
MIT
JavaScript
Oct 21, 2026
dsh plugin --profile web add dsh-plugin-trace-insightby sublatesublate-design
Windows environment diagnostics for DeepSeek Harness
★ 0
MIT
TypeScript
Aug 14, 2026
dsh plugin --profile web add dsh-doctor-windowsby whitequeen306
Project housekeeping for DeepSeek Harness: 12 /logi-* commands, seven specialist review subagents, health score, and a baseline gate.
★ 15
↓ 3.6k/wk
MIT
JavaScript
Nov 6, 2026
dsh plugin --profile web add dsh-logistics