Skip to content

Conversation

@davidbuzinski
Copy link
Member

@davidbuzinski davidbuzinski commented Oct 8, 2024

This change is so that we no longer rely on upx to compress the run-matlab-command binary. We were doing this in order to get our extension below the size limit to publish on the marketplace.

It is updated to zip all of the run-matlab-command binaries that we ship in the extension. During all of the "run" steps, we will unzip the binary if it hasn't already been unzipped. It adds a small amount of overhead and maintenance, but ensures that we do not add any further external dependencies onto the runner for our Tasks.

I am also commenting out the failing parallel tests steps until the issue mentioned in the comment is resolved.

@davidbuzinski davidbuzinski changed the title DRAFT: update run-matlab-command compression Update run-matlab-command compression Oct 9, 2024
Comment on lines +17 to +19
tr.registerMock("fs", {
chmodSync: () => Promise.resolve(0),
});
Copy link
Member

Choose a reason for hiding this comment

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

Huh, was this failing before? Or did it just work even with that not mocked out?

Copy link
Member Author

Choose a reason for hiding this comment

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

It was working. It was just operating on the actual file. This time the file didn't exist (because it needs to be unzipped) so it was failing. I wanted to make sure our tests don't ever actually unzip anything so we don't accidentally ship both the zip and the unzipped binary

@davidbuzinski davidbuzinski merged commit 99cca12 into master Oct 9, 2024
1 check passed
@davidbuzinski davidbuzinski deleted the update-rmc-compression branch October 9, 2024 20:24
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