Fix GreedyBatchedCTCInfer regression from GreedyCTCInfer. (#9347)

[titu1994]

• Fix GreedyBatchedCTCInfer regression from GreedyCTCInfer.

decoder_lengths is allowed to be on CPU even when decoder_output is on GPU. This matches the behavior of GreedyCTCInfer. Even though that behavior is unintentional, there is code depending on that behavior, including our jupyter notebooks.

Signed-off-by: Daniel Galvez [email protected]

• Apply isort and black reformatting

Signed-off-by: titu1994 [email protected]

---

Signed-off-by: Daniel Galvez [email protected]
Signed-off-by: titu1994 [email protected]
Co-authored-by: Somshubra Majumdar [email protected]
Co-authored-by: titu1994 [email protected]
Co-authored-by: Nithin Rao [email protected]
(cherry picked from commit aed9d07)

What does this PR do ?

Information is here - #9347

GitHub Actions CI

The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.

The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".

Before your PR is "Ready for review"

Pre checks:

• Make sure you read and followed Contributor guidelines
• Did you write any new necessary tests?
• Did you add or update any necessary documentation?
• Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
  • Reviewer: Does the PR have correct import guards for all optional libraries?

PR Type:

• New Feature
• Bugfix
• Documentation

If you haven't finished some of the above items you can still open "Draft" PR.

Who can review?

Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.

Additional Information

• Related to # (issue)