Skip to content

Conversation

@viviveevee
Copy link
Contributor

Fixes #273

@viviveevee viviveevee marked this pull request as ready for review January 21, 2026 09:52
@viviveevee viviveevee requested a review from a team as a code owner January 21, 2026 09:52
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd like to avoid committing large binaries to the repo if possible.

A few questions:

  • How was this 3MB Wasm module generated?
  • Could we replace it with a script or dummy project that generates the binary at build/test time?

If we don't need to verify canister installation by making actual calls (i.e., the module doesn't need functional endpoints), we could generate a dummy Wasm module padded to the required size. Something like a minimal module with a large data segment would be valid Wasm but contain no real logic.

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.

Error during deployment of large size canister modules

2 participants