fix: attempt to fix parsing of tricky template files

[evan-onyx]

Description

There are exceedingly rare cases where certain template files in drive have a mimetype provided by google drive that differs from the mimetype extracted from within the file that causes a ValueError to be raised when they are processed by python-docx. Now we catch these errors and attempt to parse as raw text.

How Has This Been Tested?

n/a, worst case is we get a different error

Backporting (check the box to trigger backport action)

Note: You have to check that the action passes, otherwise resolve the conflicts manually and tag the patches.

• This PR should be backported (make sure to check that the backport attempt succeeds)
• [Optional] Override Linear Check

---

Summary by cubic

Fixed an error when parsing rare template files with mismatched mimetypes by catching ValueError and falling back to reading as raw text.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
internal-search	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 25, 2025 0:51am

[greptile-apps]

Greptile Summary

This PR enhances error handling in the docx_to_text_and_images function within the file processing module. The change expands the exception catching from just BadZipFile to include ValueError exceptions when processing DOCX files with python-docx.

The modification addresses a specific edge case with Google Drive template files where there's a mismatch between the MIME type provided by Google Drive and the actual file content structure. When python-docx encounters these inconsistencies, it raises a ValueError instead of the previously handled BadZipFile exception.

The fix follows the existing error handling pattern in the codebase - when either exception occurs, the system logs a warning and gracefully degrades to parsing the file as plain text using the read_text_file function with proper encoding detection. This maintains the robustness of the document processing pipeline by ensuring files don't fail completely due to format inconsistencies, particularly important for the Google Drive connector integration described in the related documentation.

Confidence score: 4/5

• This is a safe defensive programming change that expands existing error handling without breaking current functionality
• The change follows established patterns in the codebase and maintains the same fallback behavior
• The file needs attention to ensure the ValueError catching doesn't mask other legitimate validation errors that should bubble up

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}

[cubic-dev-ai]

cubic analysis

No issues found across 1 file. Review in cubic