You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bot gets disconnected from the network and fails to restart after triggering an error produced by command list configs:
/opt/conda/envs/hummingbot/lib/python3.6/asyncio/events.py:145: RuntimeWarning:
coroutine 'ERC20Token.get_decimals' was never awaited
self._callback(*self_args)
Test 1
Sending list configs command will show an error in running logs:
- root - ERROR - Unhandled error in background task: unsupported operand type(s) for +=:
'NoneType' and 'str' (See log file for stack trace dump)
Trace dump:
2019-09-25 01:13:02,451 - root - ERROR - Unhandled error in background task: unsupported operand type(s) for +=: 'NoneType' and 'str'
Traceback (most recent call last):
File "/hummingbot/core/utils/async_call_scheduler.py", line 80, in _coro_scheduler
fut.set_result(await coro)
File "/opt/conda/envs/hummingbot/lib/python3.6/concurrent/futures/thread.py", line 56, in run
result = self.fn(*self.args, **self.kwargs)
File "/hummingbot/notifier/telegram_notifier.py", line 185, in <lambda>
reply_markup=reply_markup
File "/opt/conda/envs/hummingbot/lib/python3.6/site-packages/telegram/bot.py", line 65, in decorator
result = func(self, *args, **kwargs)
File "/opt/conda/envs/hummingbot/lib/python3.6/site-packages/telegram/bot.py", line 90, in decorator
result = self._request.post(url, data, timeout=kwargs.get('timeout'))
File "/opt/conda/envs/hummingbot/lib/python3.6/site-packages/telegram/utils/request.py", line 309, in post
headers={'Content-Type': 'application/json'})
File "/opt/conda/envs/hummingbot/lib/python3.6/site-packages/telegram/utils/request.py", line 223, in _request_wrapper
raise BadRequest(message)
telegram.error.BadRequest: Message must be non-empty
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/hummingbot/core/utils/async_utils.py", line 8, in safe_wrapper
return await c
File "/hummingbot/core/utils/async_call_scheduler.py", line 92, in _coro_scheduler
app_warning_msg += f" [[Got exception: {str(e)}]]"
TypeError: unsupported operand type(s) for +=: 'NoneType' and 'str'
The bot will continue to cancel and place orders but will start to get errors like markets are offline, eth wallet not connected, NetworkStatus.NOT_CONNECTED.
Stopping and restarting the strategy will give an error:
/opt/conda/envs/hummingbot/lib/python3.6/asyncio/events.py:145: RuntimeWarning:
coroutine 'ERC20Token.get_decimals' was never awaited
self._callback(*self_args)
Test 2 (Binance)
Performed test with the same steps on a different exchange (Binance). Command list config will show an error in running logs but it did not give a run time warning as seen on IDEX when restarted. Bot continued to behave as expected.
Release version
Tests have been performed on both latest and development version.
Describe the bug
Bot gets disconnected from the network and fails to restart after triggering an error produced by command
list configs
:Test 1
Sending
list configs
command will show an error in running logs:Trace dump:
The bot will continue to cancel and place orders but will start to get errors like markets are offline, eth wallet not connected, NetworkStatus.NOT_CONNECTED.
Stopping and restarting the strategy will give an error:
Test 2 (Binance)
Performed test with the same steps on a different exchange (Binance). Command
list config
will show an error in running logs but it did not give a run time warning as seen on IDEX when restarted. Bot continued to behave as expected.Release version
Tests have been performed on both latest and development version.
"branch": "master",
"commit": "4941ec38b8090b8f458d19ca5ad98d667f561b4e",
"date": "2019-09-23T17:29:45Z",
"branch": "development",
"commit": "69d71a42e1ad42c72320360d1fd4dc78f8aeae4a",
"date": "2019-09-23T17:57:25Z",
Attachments
Strategy config file:
conf_pmm_base-eth.txt
Log file:
hummingbot_logs_2019-09-25-00-01-56.log
The text was updated successfully, but these errors were encountered: