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

Regression in forge script, fuzz: could not fetch slot {idx} from {address} #6855

Closed
2 tasks done
Thegaram opened this issue Jan 19, 2024 · 3 comments
Closed
2 tasks done
Labels
T-bug Type: bug

Comments

@Thegaram
Copy link

Component

Forge

Have you ensured that all of these are up to date?

  • Foundry
  • Foundryup

What version of Foundry are you on?

d46bcb3

What command(s) is the bug in?

forge script

Operating System

macOS (Apple Silicon)

Describe the bug

Regression in d46bcb3 (#6219). When I install the previous commit (02292f2) using foundryup --commit the issue goes away.

> forge script --legacy scripts/foundry/InitializeL2BridgeContracts.s.sol:InitializeL2BridgeContracts --rpc-url "$SCROLL_L2_DEPLOYMENT_RPC" 2>&1
[⠊] Compiling...
[⠘] Compiling 261 files with 0.8.16
[⠢] Solc 0.8.16 finished in 17.54s
2024-01-19T14:27:30.019085Z ERROR sharedbackend: Failed to send/recv `storage` err=failed to get storage for 0x5300000000000000000000000000000000000000 at 82: could not fetch slot {idx} from {address} address=0x5300000000000000000000000000000000000000 index=82
Error: 
fuzz: failed to inspect: Database error: failed to get storage for 0x5300000000000000000000000000000000000000 at 82: could not fetch slot {idx} from {address}

A similar command works with ethereum/client-go:v1.11.6 but not with scrolltech/l2geth:scroll-v5.1.7 (which is a fork of geth). It is possible that alloy providers rely on some RPC features not widely supported.

@Thegaram Thegaram added the T-bug Type: bug label Jan 19, 2024
@Evalir
Copy link
Member

Evalir commented Jan 19, 2024

Right, is it possible for you to provide a small repro where we can isolate this case? This way we can take a look at it

@DaniPopes
Copy link
Member

DaniPopes commented Jan 19, 2024

@Thegaram This may have been fixed with #6857, can you try again with foundryup -b master or in the next nightly?

@Thegaram
Copy link
Author

Yes, tested with master (5ea2c5e), it works now, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-bug Type: bug
Projects
Archived in project
Development

No branches or pull requests

3 participants