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

Database Error #64

Open
dmarzzz opened this issue Dec 18, 2024 · 0 comments
Open

Database Error #64

dmarzzz opened this issue Dec 18, 2024 · 0 comments

Comments

@dmarzzz
Copy link
Member

dmarzzz commented Dec 18, 2024

I ran

contender % cargo run setup ./scenarios/stress.toml http://experi-proxy-dcb3yn8uzjpc-196463883.us-east-2.elb.amazonaws.com  

and got

     Running `target/debug/contender setup ./scenarios/stress.toml 'http://***.com'`
No private keys provided. Using default private keys.
deploying contract: "SpamMe3"
thread 'tokio-runtime-worker' panicked at /Users/***/***/tools/contender/crates/core/src/test_scenario.rs:191:22:
failed to send tx: ErrorResp(ErrorPayload { code: -32000, message: "already known", data: None })
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: DatabaseError: join error; callback crashed task 16 panicked with message "failed to send tx: ErrorResp(ErrorPayload { code: -32000, message: \"already known\", data: None })"
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

No branches or pull requests

1 participant