feat: adding near-sandbox with new runner to start server #68
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
austinabell
approved these changes
Jul 23, 2021
There was a problem hiding this comment.
Sooo cool, this is expected right?
Receipt: 2RAu3ZWPQbUf3ESyyWSE9ofEmRZcFDqeMpmJrkKAFhJH
Log [status-message.test.near]: A
Log [status-message.test.near]: A
Log [status-message.test.near]: A
Receipt: 9vYMzUmLWpnR5GyBVRTkVFYayzpbvGa8RsPfevTvf6wh
Log [status-message.test.near]: A
Log [status-message.test.near]: A
Log [status-message.test.near]: A
|
@austinabell Yep! |
results unwrapped by default now
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Example of using new test runner to start up and close server. Still a WIP. I need to figure out the best way to close server gracefully. Currently
server.close()kills the process and ends the current process.