Fix: ml/engine/utils/FileUtils casts long file length to int incorrectly

[maxlepikhin]

Description

"(int) file.length()" makes length negative for file sizes greater than 2GB (but less than 4GB). This results in function returning empty list of chunks and model registration task being stuck in CREATED state.

The fix is to use longs when splitting model zip file. Tested locally that updated opensearch-ml-algorithms jar fixes the problem.

Bug: #3197

Related Issues

N/A

Check List

• New functionality includes testing.
• New functionality has been documented.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[pyek-bot]

Should we create an issue for this and link it to the PR? @ylwu-amzn

Edit: I see that it is here already #3197
@maxlepikhin can you add it to the description?

[mingshl]

@maxlepikhin in every commit, you need to commit with your sign off using -s, for example. git commit -m"commit message" -s

Your last two commits are missing sign off, you can fix it by the following:

To add your Signed-off-by line to every commit in this branch:

Ensure you have a local copy of your branch by checking out the pull request locally via command line.
In your local branch, run: git rebase HEAD~2 --signoff
Force push your changes to overwrite the branch: git push --force-with-lease origin fix-3197

[b4sjoo]

Seems need to run spotlessApply

[brianf-aws]

Hey @maxlepikhin ! Just curious, how did you debug this?

[maxlepikhin]

Hey @maxlepikhin ! Just curious, how did you debug this?

By reading the code.

[mingshl]

rerunning the flaky IT test for linux

[maxlepikhin]

rerunning the flaky IT test for linux

@mingshl it appears to be waiting on some human action, what is the next step here?

[brianf-aws]

rerunning the flaky IT test for linux

@mingshl it appears to be waiting on some human action, what is the next step here?

Hey Max, reaching out to team internally to run the job again. Apologies for the late response.

[mingshl]

will approve after all tests passed.

@maxlepikhin can you identify the version when this bug is happening? trying to figure out the backport versions cc @ylwu-amzn

[maxlepikhin]

will approve after all tests passed.

@maxlepikhin can you identify the version when this bug is happening? trying to figure out the backport versions cc @ylwu-amzn

From 11/17/22 (bfb0748): all releases it seems. It'd be great if somebody from the maintainers can help the tests pass, are they flaky?