populus.utils.compat.compat_stdlib.Timeout: 120 seconds about smart-contracts HOT 10 CLOSED

This is probably because of Populus that sets default timeouts in a few places. See https://github.com/ethereum/populus/search?q=timeout&unscoped_q=timeout .

from smart-contracts.

I have opened ethereum/populus#464 to fix this issue

from smart-contracts.

is there a workaround/solution in the interim to address this ?

from smart-contracts.

@troowala Let me see if I can monkey match some code in the ico repo to increase the timeout.

from smart-contracts.

thanks mate , i have tried increasing every timeout value in every file in the ico directory by 100X but still get the same issue. also ocassionally some contracts do end up deploying and then it bails halfway through with these timeout issues on mainnet but never on ropsten.

im not even using the confirm_tx option so why would it behave this way ? should it not simply submit the transaction get tx hash and proceed ?

also any way to use infura or ipc instead of http provider , the populus.json doesnt get into passing the private key to infura node option nor into using an ipc path . thanks for your time on this.

from smart-contracts.

@troowala I have opened #136 to resolve the issue.

also any way to use infura

I'm fairly new to the project, so my answers might be wrong here. But from my quick read through the codebase, I think you have specify chain in your yaml file. eg: https://github.com/TokenMarketNet/ico/blob/c8d45fa4117bcb7caf756c5c3ecf736e0c3759d2/crowdsales/unit-test.yml#L7

or ipc instead of http provider

I don't think that's possible at the moment. But we could make that configurable too. Let me leave this decision to @miohtama.

from smart-contracts.

in the interim the workaround was to change the timeout values in the following files
/usr/local/lib/python3.5/dist-packages/populus/wait.py
/usr/local/lib/python3.5/dist-packages/populus/utils/wait.py

from smart-contracts.

@troowala changing timeout in just populus/wait.py wasn't sufficient? Why did you need to change values in populus/utils/wait.py?

from smart-contracts.

it looked like it was leveraging timeout values from both in different scenarios/stages of the deploy so i did, do you reckon only populus/wait.py requires the changes ?

from smart-contracts.

@troowala populus/wait.py should be sufficient. All the methods in populus/wait.py are drived through Wait class in populus/wait.py. So just setting values in populus/wait.py should be sufficient.

from smart-contracts.