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

🧪 Feat: callHandler test coverage #1232

Merged
merged 9 commits into from
Jun 21, 2024

Conversation

roninjin10
Copy link
Collaborator

@roninjin10 roninjin10 commented Jun 21, 2024

Description

Concise description of proposed changes

Testing

Explain the quality checks that have been done on the code changes

Additional Information

Your ENS/address:

Summary by CodeRabbit

  • Tests

    • Added comprehensive test cases for various functions, including cloneVmWithBlockTag, executeCall, shouldCreateTransaction, and validateCallParams.
  • Error Handling Improvements

    • Enhanced error handling in multiple error classes (BaseError, ExecutionError, GasLimitExceededError, InternalEvmError, InvalidJumpError, ForkError, NoForkUriSetError).
    • Updated constructors and error message checks for better error differentiation and management.
  • Refactor

    • Improved internal error-handling logic to handle specific error cases more effectively.

Copy link

vercel bot commented Jun 21, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
tevm-monorepo-tevm ❌ Failed (Inspect) Jun 21, 2024 8:37pm

Copy link

changeset-bot bot commented Jun 21, 2024

🦋 Changeset detected

Latest commit: 2f95bb8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 30 packages
Name Type
@tevm/errors Patch
@tevm/schemas Patch
@tevm/actions Patch
@tevm/jsonrpc Patch
@tevm/server Patch
@tevm/utils Patch
tevm Patch
@tevm/block Patch
@tevm/procedures Patch
@tevm/state Patch
@tevm/tx Patch
@tevm/vm Patch
@tevm/viem Patch
@tevm/client-types Patch
@tevm/decorators Patch
@tevm/base-client Patch
@tevm/blockchain Patch
@tevm/http-client Patch
@tevm/ethers Patch
@tevm/common Patch
@tevm/contract Patch
@tevm/evm Patch
@tevm/memory-client Patch
@tevm/precompiles Patch
@tevm/predeploys Patch
@tevm/receipt-manager Patch
@tevm/txpool Patch
@tevm/sync-storage-persister Patch
@tevm/experimental-solc Patch
@tevm/test-utils Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link
Contributor

coderabbitai bot commented Jun 21, 2024

Important

Review skipped

More than 25% of the files skipped due to max files limit. The review is being skipped to prevent a low-quality review.

157 files out of 296 files are above the max files limit of 50. Please upgrade to Pro plan to get higher limits.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The updates introduce new test cases for multiple functions, enhance error handling, and refine class constructors within the codebase. Key changes include adding test files for functions like cloneVmWithBlockTag, executeCall, and shouldCreateTransaction, adjustments to the handling of specific Ethereum errors, and enhancements in error class constructors for better handling and clarity.

Changes

File Path Change Summary
packages/.../Call/cloneVmWithBlock.spec.ts Introduced tests for cloneVmWithBlockTag, validating cloning VMs, state roots, error handling, and caching blocks.
packages/.../Call/executeCall.spec.ts Added tests for executeCall, covering successful contract calls, error handling, and gas price error management.
packages/.../Call/shouldCreateTransaction.spec.ts Added tests for shouldCreateTransaction, examining behavior under various createTransaction parameters.
packages/.../Call/validateCallParams.spec.ts Introduced tests for validateCallParams, checking parameter validation and error handling for call actions.
packages/.../Call/handleEvmError.js Refactored handleRunTxError to enhance error message checks and handling, added InvalidJumpError import.
packages/errors/src/ethereum/BaseError.js Updated BaseError constructor to make args mandatory and code optional.
packages/errors/src/ethereum/ExecutionErrorError.js Added optional tag parameter to ExecutionError constructor for internal naming.
packages/.../ethereum/GasLimitExceededError.js Removed abstract indicators, checks in the constructor, and @abstract tags from GasLimitExceededError.
packages/.../ethereum/ethereumjs/InternalEvmError.js Modified InternalEvmError constructor to include an additional argument 'InternalEvmError' in super call.
packages/.../ethereum/ethereumjs/InvalidJumpError.js Updated InvalidJumpError constructor to accept optional tag parameter for error name/tag.
packages/errors/src/fork/ForkError.js Adjusted BaseError instantiation within ForkError class to alter the object passed from undefined to an empty object {}.
packages/errors/src/fork/NoForkUriSetError.js Updated NoForkTransportSetError constructor to pass an additional argument 'NoForkTransportSetError' in super call.

Poem

🐰 In a mystical realm of code,
Where bytes and blocks uphold,
Bugs and errors we outmode,
Through tests and refactoring bold.

VMs, errors, all refined,
In code they now align.
Cheers to code, redefined,
A work both clean and fine! 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@roninjin10 roninjin10 marked this pull request as ready for review June 21, 2024 03:45
Copy link
Collaborator Author

roninjin10 commented Jun 21, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @roninjin10 and the rest of your teammates on Graphite Graphite

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3b34435 and ebdb1cf.

Files ignored due to path filters (3)
  • packages/actions/src/Call/__snapshots__/cloneVmWithBlock.spec.ts.snap is excluded by !**/*.snap
  • packages/actions/src/Call/__snapshots__/executeCall.spec.ts.snap is excluded by !**/*.snap
  • packages/actions/src/Call/__snapshots__/handleEvmError.spec.ts.snap is excluded by !**/*.snap
Files selected for processing (5)
  • packages/actions/src/Call/cloneVmWithBlock.spec.ts (1 hunks)
  • packages/actions/src/Call/executeCall.spec.ts (1 hunks)
  • packages/actions/src/Call/handleEvmError.spec.ts (1 hunks)
  • packages/actions/src/Call/shouldCreateTransaction.spec.ts (1 hunks)
  • packages/actions/src/Call/validateCallParams.spec.ts (1 hunks)
Files skipped from review due to trivial changes (1)
  • packages/actions/src/Call/validateCallParams.spec.ts
Additional comments not posted (4)
packages/actions/src/Call/cloneVmWithBlock.spec.ts (1)

8-61: Comprehensive Test Coverage for cloneVmWithBlockTag

The test cases cover various scenarios like successful VM cloning, handling unavailable state roots, and error handling during cloning. This is crucial for ensuring the robustness of the cloneVmWithBlockTag function. Good use of the expect function to assert conditions and the structured approach in each test case enhances readability and maintainability of the test suite.

packages/actions/src/Call/shouldCreateTransaction.spec.ts (1)

6-69: Effective Testing of shouldCreateTransaction Function

The test cases effectively cover all potential values for createTransaction, ensuring that the function behaves as expected under various conditions. The use of parameterized testing for different values of createTransaction is a good practice as it ensures that all edge cases are covered.

packages/actions/src/Call/executeCall.spec.ts (1)

13-120: Thorough Testing of executeCall Function

The test cases are well-structured and cover a range of scenarios including successful contract calls, handling of contract call errors, and gas price errors. The use of mocked data and assertions ensures that the function's behavior is thoroughly validated under different conditions. This contributes significantly to the reliability and stability of the executeCall function.

packages/actions/src/Call/handleEvmError.spec.ts (1)

46-165: Comprehensive Error Handling Tests in handleRunTxError

The tests for handleRunTxError are comprehensive, covering unknown errors, known error types, EvmError instances, and specific EvmError subclasses. The use of a variety of error instances and the structured approach to testing each one ensures that the function can handle a wide range of error scenarios effectively.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ebdb1cf and 9ec3c27.

Files ignored due to path filters (2)
  • packages/actions/src/Call/__snapshots__/handleEvmError.spec.ts.snap is excluded by !**/*.snap
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (9)
  • packages/actions/src/Call/handleEvmError.js (3 hunks)
  • packages/actions/src/Call/handleEvmError.spec.ts (1 hunks)
  • packages/errors/src/ethereum/BaseError.js (2 hunks)
  • packages/errors/src/ethereum/ExecutionErrorError.js (2 hunks)
  • packages/errors/src/ethereum/GasLimitExceededError.js (4 hunks)
  • packages/errors/src/ethereum/ethereumjs/InternalEvmError.js (1 hunks)
  • packages/errors/src/ethereum/ethereumjs/InvalidJumpError.js (1 hunks)
  • packages/errors/src/fork/ForkError.js (1 hunks)
  • packages/errors/src/fork/NoForkUriSetError.js (1 hunks)
Additional context used
Biome
packages/actions/src/Call/handleEvmError.spec.ts

[error] 121-121: Do not shadow the global "constructor" property. (lint/suspicious/noShadowRestrictedNames)

Consider renaming this variable. It's easy to confuse the origin of variables when they're named after a known global.

Additional comments not posted (5)
packages/errors/src/ethereum/ExecutionErrorError.js (1)

49-57: Good practice: Inclusion of discriminative tag in constructor.

The addition of an optional tag parameter in the ExecutionError constructor is a good practice for better error discrimination. The constructor is well-structured and aligns with best practices.

packages/errors/src/fork/ForkError.js (1)

75-75: Improved error instantiation and handling

The change to instantiate BaseError with an empty object {} if no cause is provided ensures consistent and predictable error handling. This is a good practice and enhances the robustness of error management.

packages/errors/src/ethereum/ethereumjs/InvalidJumpError.js (1)

74-83: Enhanced flexibility in error tagging

Allowing an optional tag parameter in the constructor enhances flexibility in error handling and logging. This change allows for more granular control over error categorization, which can be beneficial in complex systems.

packages/errors/src/ethereum/BaseError.js (1)

44-44: Required arguments in error constructor enhance robustness

Requiring the args parameter in the constructor ensures that essential information is not omitted, enhancing the robustness and clarity of error instantiation. This is a good practice in error handling.

packages/actions/src/Call/handleEvmError.js (1)

127-138: Ensure proper error handling for non-EVM errors.

The function handleRunTxError defaults to returning InternalEvmError for any unrecognized error. This catch-all approach may obscure the underlying issue if the error does not fit any known EVM error category. Ensure that this behavior is intentional and consider logging or handling these cases more explicitly to aid in debugging and error tracking.

Verification successful

The handleRunTxError function is used in executeCall.js to process errors and return them in the errors array. The function defaults to returning InternalEvmError for any unrecognized error, including logging certain conditions.

Given the current implementation, the behavior of defaulting to InternalEvmError appears intentional. However, the review comment suggests ensuring this behavior is intentional and considering more explicit logging or handling for non-EVM errors.

  • packages/actions/src/Call/handleEvmError.js: The function logs when an error is not a valid EvmError or when no error constructor is found.

The current implementation does include logging for these specific cases, which aids in debugging and error tracking.

Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify that InternalEvmError is the intended default for unknown errors and check if there's a need for more explicit handling.

# Test: Search for the function usage. Expect: Proper handling or logging of unknown errors.
rg --type javascript $'handleRunTxError'

Length of output: 74



Script:

#!/bin/bash
# Description: Verify that InternalEvmError is the intended default for unknown errors and check if there's a need for more explicit handling.

# Test: Search for the function usage. Expect: Proper handling or logging of unknown errors.
rg --type js $'handleRunTxError'

Length of output: 315



Script:

#!/bin/bash
# Extract the implementation of handleRunTxError from handleEvmError.js
ast-grep --lang javascript --pattern $'export const handleRunTxError = (e) => {
  $$$
}' packages/actions/src/Call/handleEvmError.js

Length of output: 3787



Script:

#!/bin/bash
# Extract the relevant code from executeCall.js where handleRunTxError is used
rg -A 10 'handleRunTxError' packages/actions/src/Call/executeCall.js

Length of output: 497

Comment on lines +102 to +127
if (e instanceof Error) {
if (e.message.includes("is less than the block's baseFeePerGas")) {
return new InvalidGasPriceError(e.message, { cause: e })
}
if (e.message.includes('invalid sender address, address is not an EOA (EIP-3607)')) {
return new InvalidAddressError(e.message, { cause: e })
}
if (e.message.includes('is lower than the minimum gas limit')) {
return new InvalidGasLimitError(e.message, { cause: e })
}
if (e.message.includes('tx has a higher gas limit than the block')) {
return new GasLimitExceededError(e.message, { cause: e })
}
if (e.message.includes('block has a different hardfork than the vm')) {
return new MisconfiguredClientError(e.message, { cause: /** @type {any}*/ (e) })
}
if (e.message.includes("the tx doesn't have the correct nonce.")) {
return new InvalidNonceError(e.message, { cause: e })
}
if (e.message.includes("sender doesn't have enough funds to send tx.")) {
return new InsufficientBalanceError(e.message, { cause: /** @type {any}*/ (e) })
}
if (e.message.includes("sender doesn't have enough funds to send tx. The upfront cost is")) {
return new InsufficientBalanceError(e.message, { cause: /** @type {any}*/ (e) })
}
return new InternalEvmError(e.message, { cause: /** @type {any}*/ (e) })
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Optimize error handling logic for clarity and maintainability.

The function handleRunTxError uses multiple if statements to check the error message and map it to a specific error class. This approach is prone to error and difficult to maintain as the number of conditions grows. Consider using a dictionary or map to associate error messages with their corresponding error classes, which can simplify the code and make it easier to manage.

- if (e.message.includes("is less than the block's baseFeePerGas")) {
-     return new InvalidGasPriceError(e.message, { cause: e })
- }
- // other conditions...
+ const errorMap = {
+     "is less than the block's baseFeePerGas": InvalidGasPriceError,
+     "invalid sender address, address is not an EOA (EIP-3607)": InvalidAddressError,
+     // other mappings...
+ };
+ 
+ const errorClass = Object.keys(errorMap).find(key => e.message.includes(key));
+ if (errorClass) {
+     return new errorMap[errorClass](e.message, { cause: e });
+ }
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
if (e instanceof Error) {
if (e.message.includes("is less than the block's baseFeePerGas")) {
return new InvalidGasPriceError(e.message, { cause: e })
}
if (e.message.includes('invalid sender address, address is not an EOA (EIP-3607)')) {
return new InvalidAddressError(e.message, { cause: e })
}
if (e.message.includes('is lower than the minimum gas limit')) {
return new InvalidGasLimitError(e.message, { cause: e })
}
if (e.message.includes('tx has a higher gas limit than the block')) {
return new GasLimitExceededError(e.message, { cause: e })
}
if (e.message.includes('block has a different hardfork than the vm')) {
return new MisconfiguredClientError(e.message, { cause: /** @type {any}*/ (e) })
}
if (e.message.includes("the tx doesn't have the correct nonce.")) {
return new InvalidNonceError(e.message, { cause: e })
}
if (e.message.includes("sender doesn't have enough funds to send tx.")) {
return new InsufficientBalanceError(e.message, { cause: /** @type {any}*/ (e) })
}
if (e.message.includes("sender doesn't have enough funds to send tx. The upfront cost is")) {
return new InsufficientBalanceError(e.message, { cause: /** @type {any}*/ (e) })
}
return new InternalEvmError(e.message, { cause: /** @type {any}*/ (e) })
if (e instanceof Error) {
const errorMap = {
"is less than the block's baseFeePerGas": InvalidGasPriceError,
"invalid sender address, address is not an EOA (EIP-3607)": InvalidAddressError,
"is lower than the minimum gas limit": InvalidGasLimitError,
"tx has a higher gas limit than the block": GasLimitExceededError,
"block has a different hardfork than the vm": MisconfiguredClientError,
"the tx doesn't have the correct nonce.": InvalidNonceError,
"sender doesn't have enough funds to send tx.": InsufficientBalanceError,
"sender doesn't have enough funds to send tx. The upfront cost is": InsufficientBalanceError
};
const errorClass = Object.keys(errorMap).find(key => e.message.includes(key));
if (errorClass) {
return new errorMap[errorClass](e.message, { cause: e });
}
return new InternalEvmError(e.message, { cause: /** @type {any}*/ (e) });
}

ValueOverflowError,
]

errorCases.forEach((constructor) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Avoid shadowing global properties

Using constructor as a variable name shadows a global property, which can lead to confusion and potential bugs. Consider renaming this variable to something more descriptive and less likely to conflict with global properties, like errorConstructor.

- errorCases.forEach((constructor) => {
+ errorCases.forEach((errorConstructor) => {
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
errorCases.forEach((constructor) => {
errorCases.forEach((errorConstructor) => {
Tools
Biome

[error] 121-121: Do not shadow the global "constructor" property. (lint/suspicious/noShadowRestrictedNames)

Consider renaming this variable. It's easy to confuse the origin of variables when they're named after a known global.

Comment on lines 37 to 45
super(
message,
{
...args,
docsBaseUrl: 'https://tevm.sh',
docsPath: '/reference/tevm/errors/classes/noforktransportseterror/',
},
'NoForkTransportSetError',
)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Refactor suggestion for constructor parameter handling.

The constructor correctly sets default values for docsBaseUrl and docsPath. However, consider checking if these properties are already provided in args to avoid overriding them with default values.

-				docsBaseUrl: 'https://tevm.sh',
-				docsPath: '/reference/tevm/errors/classes/noforktransportseterror/',
+				docsBaseUrl: args.docsBaseUrl ?? 'https://tevm.sh',
+				docsPath: args.docsPath ?? '/reference/tevm/errors/classes/noforktransportseterror/',
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
super(
message,
{
...args,
docsBaseUrl: 'https://tevm.sh',
docsPath: '/reference/tevm/errors/classes/noforktransportseterror/',
},
'NoForkTransportSetError',
)
super(
message,
{
...args,
docsBaseUrl: args.docsBaseUrl ?? 'https://tevm.sh',
docsPath: args.docsPath ?? '/reference/tevm/errors/classes/noforktransportseterror/',
},
'NoForkTransportSetError',
)

@roninjin10 roninjin10 merged commit a170f0f into main Jun 21, 2024
15 of 16 checks passed
@roninjin10 roninjin10 deleted the 06-20-_test_tube_feat_callhandler_test_coverage branch June 21, 2024 20:42
roninjin10 pushed a commit that referenced this pull request Jun 21, 2024
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

`main` is currently in **pre mode** so this branch has prereleases
rather than normal releases. If you want to exit prereleases, run
`changeset pre exit` on `main`.

⚠️⚠️⚠️⚠️⚠️⚠️

# Releases
## @tevm/[email protected]

### Patch Changes

- [#1232](#1232)
[`a170f0f`](a170f0f)
Thanks [@roninjin10](https://github.com/roninjin10)! - Fixed issues with
error handling and added unit testing

## @tevm/[email protected]

### Patch Changes

-   Updated dependencies \[]:
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- [#1232](#1232)
[`a170f0f`](a170f0f)
Thanks [@roninjin10](https://github.com/roninjin10)! - Fixed issues with
error handling and added unit testing

- Updated dependencies
\[[`a170f0f`](a170f0f),
[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f),
[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- [#1232](#1232)
[`a170f0f`](a170f0f)
Thanks [@roninjin10](https://github.com/roninjin10)! - Fix bug with
error tags not being set properly

- [#1232](#1232)
[`a170f0f`](a170f0f)
Thanks [@roninjin10](https://github.com/roninjin10)! - Fixed issues with
error handling and added unit testing

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`6595da4`](6595da4),
[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- [#1232](#1232)
[`a170f0f`](a170f0f)
Thanks [@roninjin10](https://github.com/roninjin10)! - Fixed issues with
error handling and added unit testing

## @tevm/[email protected]

### Patch Changes

- [#1234](#1234)
[`6595da4`](6595da4)
Thanks [@roninjin10](https://github.com/roninjin10)! - Add more jsdoc to
MemoryClient docs

- Updated dependencies
\[[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f),
[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- [#1232](#1232)
[`a170f0f`](a170f0f)
Thanks [@roninjin10](https://github.com/roninjin10)! - Fixed issues with
error handling and added unit testing

- Updated dependencies
\[[`a170f0f`](a170f0f),
[`6595da4`](6595da4),
[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f),
[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

-   Updated dependencies \[]:
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f),
[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- [#1232](#1232)
[`a170f0f`](a170f0f)
Thanks [@roninjin10](https://github.com/roninjin10)! - Fixed issues with
error handling and added unit testing

- Updated dependencies
\[[`a170f0f`](a170f0f),
[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

- Updated dependencies
\[[`a170f0f`](a170f0f),
[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## @tevm/[email protected]

### Patch Changes

-   Updated dependencies \[]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]

## [email protected]

### Patch Changes

- [#1232](#1232)
[`a170f0f`](a170f0f)
Thanks [@roninjin10](https://github.com/roninjin10)! - Fixed issues with
error handling and added unit testing

- Updated dependencies
\[[`a170f0f`](a170f0f),
[`6595da4`](6595da4),
[`a170f0f`](a170f0f)]:
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]
    -   @tevm/[email protected]

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
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