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

fully remove 'sim-chain' #9725

Open
turadg opened this issue Jul 17, 2024 · 0 comments
Open

fully remove 'sim-chain' #9725

turadg opened this issue Jul 17, 2024 · 0 comments
Labels
enhancement New feature or request technical-debt

Comments

@turadg
Copy link
Member

turadg commented Jul 17, 2024

What is the Problem Being Solved?

sim-chain is a function that we used to have to run the chain without agd but now we use agd and Docker liberally. (See #9480 (comment) )

We've removed it from user docs but it has remnants in code. These create complexity and increase costs of code maintenance. There are too many things not implemented, and not simulated. There's also been some confusion about what parts are supposed to still work.

Description of the Design

Remove all references to sim-chain.

@mhofman writes,

Testing of JS cosmic swingset should likely use a fake/mock chain that I would personally consider a sim chain on steroids. It would implement mocks of vstorage and other cosmos modules.

Related:

Security Considerations

Scaling Considerations

Test Plan

Upgrade Considerations

@turadg turadg added enhancement New feature or request technical-debt labels Jul 17, 2024
mergify bot added a commit that referenced this issue Jul 26, 2024
refs: #9725

## Description
On the path to,
- #9725 

Remove concessions in SwingSet to `@agoric/cosmic-swingset/src/sim-chain.js` by requiring a bridgeDevice.

Since `sim-chain` is no longer supported, we remove the ability to use it from `@agoric/solo`.  This makes several of the tests in `@agoric/solo` fail, so we skip those that relied on `sim-chain`, while continuing to test the `ag-solo` basic functionality.   We don't remove `@agoric/solo` because it serves as an example of a non-chain SwingSet application, and @michaelfig would like to refactor it into a configuration of a general `agvm` program.

### Security Considerations
none

### Scaling Considerations
none

### Documentation Considerations
none

### Testing Considerations
CI suffices

### Upgrade Considerations

On-chain uses always provide a bridge device. This does affect line numbers. It will go out with the next kernel upgrade.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request technical-debt
Projects
None yet
Development

No branches or pull requests

1 participant