🥅(summary) catch unexpected file-related exceptions when handling recording objects

[lebaudantoine]

Previously, if a recording file was not found in the bucket, the code would crash. This adds proper error handling to avoid unhandled failures.

[lebaudantoine]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.

[coderabbitai]

Walkthrough

A new FileServiceException class was added to summary.core.file_service and _download_from_minio now catches MinioException and S3Error, re-raising them as FileServiceException. In summary.core.celery_worker, process_audio_transcribe_summarize_v2 wraps audio preparation and transcription calls in a try/except that catches FileServiceException, logs and returns early on error, and records transcription start/end times in metadata. An import for FileServiceException was added to the worker module.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: adding exception handling for file-related errors when processing recording objects, which aligns with the changeset that introduces FileServiceException and wraps file operations in try-catch blocks.
Description check	✅ Passed	The description is directly related to the changeset, explaining the motivation for the changes (preventing crashes when recording files are not found) and describing the solution (adding proper error handling).
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@src/summary/summary/core/celery_worker.py`:
- Line 178: The logged full transcription (the logger.debug call that prints the
variable transcription) exposes potential PII; remove the direct transcription
output and replace it with a safe alternative such as logging only metadata
(e.g., transcription length, language, and a truncated/redacted snippet like
transcription[:100] + '...[REDACTED]') or a non-reversible hash/checksum of
transcription. Locate the logger.debug("Transcription: \n %s", transcription)
call in celery_worker.py and update it to log only redacted/derived info (or
remove the log entirely) while ensuring the variable name transcription is not
interpolated into logs.

[coderabbitai]

✅ Actions performed

Full review triggered.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud