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

sham non-trapping shim and ponyfill for cross-repo testing #2683

Draft
wants to merge 3 commits into
base: markm-prepare-for-stabilize-2
Choose a base branch
from

Conversation

erights
Copy link
Contributor

@erights erights commented Jan 4, 2025

Staged on #2679

Sham version of #2673 , where all the code in the new non-trapping package of #2673 has been moved into corresponding subdirectories of ses. This is in order to fix the following:

Currently, at Agoric/agoric-sdk#9201 we have the directive

#endo-branch: markm-use-no-trapping-shim

which refers to #2675 that builds on #2673. However, it doesn't work with the following pervasive error:

error Couldn't find package "@endo/non-trapping-shim@^0.1.0" required by "ses@file:/home/runner/endo/packages/ses/ses-v1.10.0-dfaf0dd3ea6bf73b5fbe2ca4bf2e9aca8823be7f.tgz" on the "npm" registry.

This is likely because there is no @endo/non-trapping package registered at npm, and there won't be until an endo with #2673 or something like it gets released. This PR works around that problem by not introducing the shim/ponyfill as a separate package, so that we can try the #endo-branch: directive, in order to see the problems that #2675 will cause for agoric-sdk, and correct them early.

@erights erights self-assigned this Jan 4, 2025
@erights erights changed the base branch from master to markm-prepare-for-stabilize-2 January 4, 2025 20:57
@erights erights changed the title Markm sham no trapping sham no-trapping shim and ponyfill for cross-repo testing Jan 4, 2025
@erights erights changed the title sham no-trapping shim and ponyfill for cross-repo testing sham non-trapping shim and ponyfill for cross-repo testing Jan 4, 2025
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.

1 participant