-
Notifications
You must be signed in to change notification settings - Fork 45
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
deploy_tester_contract() does not reveal the error message #1329
Comments
This is because |
The documentation of |
It's not special because it's a constructor. I was just using |
This commit modifies `deploy_tester_contract()` so it raises an exception with a message with failed `require()`s. Before this commit, `deploy_tester_contract()` did not raise an exception when the deployment failed for a `require()` condition. This solves raiden-network#1329.
This commit modifies `deploy_tester_contract()` so it raises an exception with a message with failed `require()`s. Before this commit, `deploy_tester_contract()` did not raise an exception when the deployment failed for a `require()` condition. This solves raiden-network#1329.
This commit modifies `deploy_tester_contract()` so it raises an exception with a message with failed `require()`s. Before this commit, `deploy_tester_contract()` did not raise an exception when the deployment failed for a `require()` condition. This solves raiden-network#1329.
Web3.py's ContractConstructor does not have |
When
deploy_tester_contract()
causes arequire()
failure,deploy_tester_contract()
raises an exception, but the exception does not contain the error message inrequire()
.This issue keeps track of fixing
deploy_tester_contract()
so that it raises an exception with the error message.The text was updated successfully, but these errors were encountered: