Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not apply MTA archive size limit for transports with multiple MTAs #1551

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

Yavor16
Copy link
Contributor

@Yavor16 Yavor16 commented Oct 23, 2024

No description provided.

Copy link
Contributor

@IvanBorislavovDimitrov IvanBorislavovDimitrov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In my opinion instead of this checks
-> Always split the appArchiveId (even in CTS processes it is set -> it might be also comma separated)
-> Just calculate all extensionDescriptors + appArchiveId (all ext descriptors size is not likely to be large)

Comment on lines 139 to 141
if (sizeOfAFile >= maxFileSizeLimit) {
deleteFile(context, fileEntry);
throw new ContentException(Messages.SIZE_OF_ALL_OPERATIONS_FILES_0_EXCEEDS_MAX_UPLOAD_SIZE_1, sizeOfAFile, maxFileSizeLimit);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will throw the exception and not check for the other files

Copy link
Contributor

@theghost5800 theghost5800 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My idea for validation improvement was to get somehow file entries/ids which will be currently used for this operation and check them in the same way as it is now. Take a look StartMtaDeploySubProcessStep class how file entries are set before to start xs2-deploy or xs2-bg-deploy process diagrams.

@Yavor16 Yavor16 force-pushed the fix-file-calculation branch 3 times, most recently from b69c748 to 3c3fc92 Compare October 28, 2024 13:57
@Yavor16 Yavor16 force-pushed the fix-file-calculation branch from 3c3fc92 to 2c01eee Compare October 28, 2024 14:35
Copy link
Contributor

@theghost5800 theghost5800 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do not forget to squash the commits into one

@Yavor16 Yavor16 force-pushed the fix-file-calculation branch from e9061c1 to f693ddf Compare November 11, 2024 13:05
Copy link

@Yavor16 Yavor16 merged commit c56b68e into master Nov 11, 2024
6 checks passed
@Yavor16 Yavor16 deleted the fix-file-calculation branch November 11, 2024 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants