fix(tika): disable external parser startup probes on Windows#1171
fix(tika): disable external parser startup probes on Windows#1171ksaurabhAparavi wants to merge 1 commit into
Conversation
📝 WalkthroughWalkthroughConfigBuilder now removes ChangesCompositeExternalParser exclusion from Tika config
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🤖 Internal: Discord sync markerAuto-managed by the Discord notification workflow. Stores the linked Discord message ID. Do not edit or delete. |
Exclude Tika's CompositeExternalParser from the generated config so clean Windows installs stop logging missing 'sox' executable errors during parser startup. Adds a regression test keeping the external parser composite out of the configured parser tree. Fixes rocketride-org#1158
f79898b to
bc8d191
Compare
Summary
soxexecutable errors at startup because Tika'sCompositeExternalParserprobes external parsers.CompositeExternalParserfrom the generated config; add a regression test keeping it out of the configured parser tree.Testing
./builder test) — relying on GitHub Actions; not runnable in the contributor's local shell (engine build / Maven / torch unavailable). Static checks (compile, no conflict markers) pass.Linked Issue
Fixes #1158