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

Publish Error: MovePackageTooBig { object_size: 102514, max_object_size: 102400 } #20107

Open
wowok-ai opened this issue Oct 31, 2024 · 5 comments
Assignees
Labels
doc-issue Issue submitted using the Doc issue template move

Comments

@wowok-ai
Copy link

It is highly recommended to expand the size of the package, such as 150K or 200K. We have split the Package, but the core part of the business is completely dependent and technically cannot be split again.
img_v3_02g6_1cd755d3-529a-4fa7-88cc-0824e16eec2g
img_v3_02g1_ab24e642-e8f6-4303-82fd-f4bb9f67a18g

@wowok-ai wowok-ai added the doc-issue Issue submitted using the Doc issue template label Oct 31, 2024
@stefan-mysten
Copy link
Contributor

Sorry to hear that @wowok-ai

Do you an idea of the individual modules' sizes? One problem with the size might be due to macro expansion. Reducing macro usage might help there.

@wowok-ai
Copy link
Author

wowok-ai commented Nov 4, 2024

@stefan-mysten Our business is to provide the infrastructure for AI interoperability consensus, and we have done several package splits, but the core package still exceeds the 100K contract limit. We think it makes sense for us to raise the Package size cap without considering other costs.

@wowok-ai
Copy link
Author

@stefan-mysten @ronny-mysten Since public(friend) cannot be referenced across packages (mutual declarations of compilation failures), the size of the core package depends on the on-chain limit (currently 100K in the test network), which prevents many features from being added. Are there other solutions that could help us?

@stefan-mysten
Copy link
Contributor

@wowok-ai I am not really versed in Move, so let me bring in some experts.
@sblackshear @damirka @manolisliolios @tnowacki

@sblackshear
Copy link
Collaborator

@wowok-ai, we'd be happy to help you with size reduction, but it's a bit difficult without more info. Would you be comfortable (privately) sharing a zip, or adding one of our engineers to the repo?

With as few files as the screenshot shows, I am guessing that the issue is likely to be aggressive macro expansion in one or two places that can be removed + make the package small enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-issue Issue submitted using the Doc issue template move
Projects
None yet
Development

No branches or pull requests

4 participants