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

[experimental] Create an error that the RPC can throw when there's an integer overflow #1226

Merged
merged 3 commits into from
Apr 2, 2023

Conversation

## Summary

Doing this, so that it can have its own `__tests__` folder, into which we'll put all the RPC method live tests.
…red among callers

## Summary

We're about to have a situation where multiple different test runners are going to want to use a test validator. Since we can't run more than one on the same box, we're going to have to find a way for them to share one.

The idea here is that the first caller to run this script will start the validator, and the last caller to quit will stop it. We achieve this through file locks and `bash` magic.

## Test Plan

```
./scripts/start-shared-test-validator & ./scripts/start-shared-test-validator
# Ctrl-C
fg
# Ctrl-C
```
… integer overflow

## Summary

When you pass a value _into_ the RPC that exceeds `Number.MAX_SAFE_INTEGER` we're going to throw. This is preferable to the number hitting the RPC truncated.

## Test Plan

```
pnpm test:unit:browser
pnpm test:unit:node
```
@github-actions
Copy link
Contributor

github-actions bot commented Apr 4, 2023

🎉 This PR is included in version 1.75.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link
Contributor

Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant