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

Allow publishing packages without a module #3711

Closed
wants to merge 3 commits into from

Conversation

theduke
Copy link
Contributor

@theduke theduke commented Mar 27, 2023

Removes the check that requires a module to be specified when publishing
a package.

Removed because modules should not be mandatory - packages with just a
file system, or with a command that uses the module of a dependency are
perfectly valid.

@theduke theduke requested a review from syrusakbary as a code owner March 27, 2023 11:08
@theduke theduke requested a review from Michael-F-Bryan March 27, 2023 11:09
Copy link
Contributor

@Michael-F-Bryan Michael-F-Bryan left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@theduke theduke force-pushed the publish-without-module branch 2 times, most recently from 4ca3665 to 8dca69a Compare March 27, 2023 14:48
theduke added 3 commits March 27, 2023 17:02
Removes the check that requires a module to be specified when publishing
a package.

Removed because modules should not be mandatory - packages with just a
file system, or with a command that uses the module of a dependency are
perfectly valid.
These were introduced by an older version of targz-to-pirita depending
on an older wasmer-registry
@theduke
Copy link
Contributor Author

theduke commented Mar 27, 2023

Closes #3712

@theduke
Copy link
Contributor Author

theduke commented Mar 27, 2023

@Michael-F-Bryan the changes here seem to regress the Python tests again.

@Michael-F-Bryan
Copy link
Contributor

@theduke I'm guessing the regression is because wapm-targz-to-pirita now generates WEBC v2 files and the wasmer_wasix::runner::WapmContainer can only deal with WEBC v1.

#3690 fixes that by removing the WapmContainer and using webc::compat::Container directly, but it's currently failing to load Python because it actually cares whether a path is relative or absolute and webc::v1::WebC would silently work with the relative paths given to it by Python.

@theduke theduke disabled auto-merge March 28, 2023 20:54
@theduke
Copy link
Contributor Author

theduke commented Mar 28, 2023

The package validation changes were included in #3716, since that also moves the validation code.

The webc version upgrades / deduplication should be handled in a dedicated PR.

@theduke theduke closed this Mar 28, 2023
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