Release 0.58.3

[odlbot]

Shankar Ambady

• AskTim canvas ai contentfile ingestion issue (AskTim canvas ai contentfile ingestion issue #3059) (03e59af1)

Carey P Gumaer

• use v3 enrollments endpoint on the dashboard (use v3 enrollments endpoint on the dashboard #3049) (2bf27b36)

[sentry]

Bug: The _extract_content_with_ocr function lacks exception handling. A PDF that is valid on its first page but corrupted on a later page will cause an unhandled exception.
_{Severity: HIGH}

Suggested Fix

Wrap the PDF processing logic within the _extract_content_with_ocr function in a try/except block to catch potential exceptions from pypdf, such as FileNotDecryptedError or PdfReadError. This will prevent a single malformed file from crashing the entire ETL task and allow it to be skipped gracefully.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: learning_resources/etl/utils.py#L594-L600

Potential issue: The `pdf_is_valid` function only checks the first page of a PDF. A file
with a valid first page but a corrupted or encrypted subsequent page will pass this
initial validation. When `_extract_content_with_ocr` is later called, it attempts to
count all pages via `len(PdfReader(file_path).pages)`. Because a `try/except` block was
removed in this function, an exception raised by `pypdf` (e.g., `FileNotDecryptedError`,
`PdfReadError`) on a subsequent bad page will be unhandled. This will crash the entire
ETL ingestion task for that file, whereas previously it would have been gracefully
skipped.

_{Did we get this right? 👍 / 👎 to inform future reviews.}