edr icon indicating copy to clipboard operation
edr copied to clipboard

Results 130 edr issues
Sort by recently updated
recently updated
newest added

We have multiple heuristics implemented in https://github.com/NomicFoundation/hardhat/blob/main/packages/hardhat-core/src/internal/hardhat-network/stack-traces/error-inferrer.ts We need to split the ones that decode returndata (covered in #250) from the ones that improve stack traces (covered in #261), and...

Under certain situations, Hardhat Network improves the error generated by applying source maps. This is done with heuristics, but not every heuristic does this kind of improvement. We need to...

## Definition of done - We need to define a Rust type to represent a solidity stack trace. - It should be similar to https://github.com/NomicFoundation/hardhat/blob/main/packages/hardhat-core/src/internal/hardhat-network/stack-traces/solidity-stack-trace.ts - We don't want to...

**Definition of Done** - We need a module that can decode the return data of a failed evm message/call. - There are two cases: when the ContractIdentifier can recognize the...

**Problem** We currently reinstall the stable and nightly Rust toolchains multiple times in a `hardhat-core CI` workflow run. **Definition of Done** Cache the Rust toolchain installations (both nightly and stable)...

As a developer, I want to see the API reference as a static website for `rethnet/main`'s latest code. This can be generated using Rust's toolchain

This PR adds all required trait implementations to be able to use Optimism's chain spec for a provider. > NOTE: To expedite exposing Optimism for testing in Hardhat, I didn't...

no changeset needed

Use same code path and config for Solidity test runner integration tests in both Rust and JS.

This PR resolves the following issues: - https://github.com/NomicFoundation/edr/issues/597 - https://github.com/NomicFoundation/edr/issues/601 The approach taken is the one we discussed last Tuesday to fetch and filter transactions in the provider implementation of...

This PR makes the `Provider` and `ProviderData` types chain-agnostic as well as remaining supporting types. At this point only the `L1ChainSpec` is supported for providers. The `OptimismChainSpec` will follow in...

no changeset needed