Add upper bound for prefix_int

[XiaohanZhangCMU]

Description of changes:

prefix_int can go up from 0 to infinity. We want to cap it at a large value before it exhausts the compute resources.

Issue #, if available:

Merge Checklist:

Put an x without space in the boxes that apply. If you are unsure about any checklist, please don't hesitate to ask. We are here to help! This is simply a reminder of what we are going to look for before merging your pull request.

General

• I have read the contributor guidelines
• This is a documentation change or typo fix. If so, skip the rest of this checklist.
• I certify that the changes I am introducing will be backward compatible, and I have discussed concerns about this, if any, with the MosaicML team.
• I have updated any necessary documentation, including README and API docs (if appropriate).

Tests

• I ran pre-commit on my change. (check out the pre-commit section of prerequisites)
• I have added tests that prove my fix is effective or that my feature works (if appropriate).
• I ran the tests locally to make sure it pass. (check out testing)
• I have added unit and/or integration tests as appropriate to ensure backward compatibility of the changes.

[snarayan21]

just want the error message a bit more cleaned up / clear. Otherwise lgtm

[snarayan21]

error comment still slightly confusing imo, approving though

[snarayan21]

is this what's intended?

Suggested change

	f'checks always returns `True` ' + f'you need to clean up TMPDIR.')
	f'checks always returns `True`. ' + f'You need to clean up TMPDIR.')

[snarayan21]

@XiaohanZhangCMU some linting errors