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

[Sandbox] Allow sandbox to produce blocks or "fast-forward" #4686

Open
mikedotexe opened this issue Aug 15, 2021 · 4 comments
Open

[Sandbox] Allow sandbox to produce blocks or "fast-forward" #4686

mikedotexe opened this issue Aug 15, 2021 · 4 comments
Assignees

Comments

@mikedotexe
Copy link

mikedotexe commented Aug 15, 2021

Per the discussion here: near/near-workspaces-js#1 @ailisp has mentioned that the Sandbox feature he's worked on provides patch state but not arbitrary block production to simulate "fast-forwarding" in time.

This is a type of testing that is quite difficult using the simulation tests, which will be deprecated in favor of Sandbox testing, which uses the sandbox feature flag from nearcore and can run tests against it, and eventually spoon data from testnet/mainnet into it, and more.

This is a cross-team effort where Dev Platform is hoping to have this feature implemented.

@stale
Copy link

stale bot commented Nov 13, 2021

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the S-stale label Nov 13, 2021
@bowenwang1996
Copy link
Collaborator

Fast forward time should be possible to do now with #5123

@stale
Copy link

stale bot commented Feb 14, 2022

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the S-stale label Feb 14, 2022
@stale
Copy link

stale bot commented May 22, 2022

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the S-stale label May 22, 2022
@akhi3030 akhi3030 removed the S-stale label Jul 8, 2022
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

No branches or pull requests

4 participants