cp: Fix fasttext predict call for numpy>2 (1482) into r1.1.0

[thomasdhc]

beep boop [🤖]: Hi @ayushdg 👋,

we've cherry picked #1482 into  for you! 🚀

Please review and approve this cherry pick by your convenience!

[thomasdhc]

/ok to test 63b7969

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[greptile-apps]

Greptile Overview

Greptile Summary

Cherry-picked fix from #1482 to make FastText filter compatible with numpy>2.0. Updated FastTextQualityFilter and FastTextLangId to wrap text inputs in lists when calling model.predict() and use .item() to extract scalar values from numpy arrays.

Key Changes:

• model.predict(text) → model.predict([text]) in both filter classes
• Added .item() calls to extract Python scalars from numpy array elements (score[0][0].item())
• Updated array indexing to account for the additional dimension from list-wrapped input (label[0][0] instead of label[0])

This aligns with numpy 2.0 behavior where array indexing returns numpy scalars that need explicit conversion to Python types.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• This is a straightforward cherry-pick of an already-merged fix for numpy>2.0 compatibility. The changes are minimal, well-scoped, and address a specific compatibility issue. The modifications follow a consistent pattern across both affected methods and align with the project's override dependency for numpy>=2.0.0 in pyproject.toml.
• No files require special attention

Important Files Changed

Filename	Overview
nemo_curator/stages/text/filters/fasttext_filter.py	Updated FastText predict calls to be compatible with numpy>2.0 by wrapping text inputs in lists and using .item() to extract scalar values

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}