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

[BUG] Runtime Warning on restart after sending list configs command #828

Closed
dennisocana opened this issue Sep 25, 2019 · 2 comments
Closed

Comments

@dennisocana
Copy link
Contributor

Describe the bug

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)

1 - list configs

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.

2 - market goes offline

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)

3 - error on restart

4- status on restart

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

@dennisocana dennisocana changed the title [BUG] IDEX Runtime Warning on restart [BUG] Runtime Warning on restart after sending list configs command Sep 27, 2019
@dennisocana
Copy link
Contributor Author

Test 3 (Bamboo Relay)

Same issue happened on a different strategy (cross-exchange) and connector.

xemm_bamboo_binance

Test 4 (DDEX)

Pure market making bot in DDEX did not show any of both errors.

@yzhang1994
Copy link
Contributor

This should have been fixed. @dennisocana let me know if you see it again.

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

2 participants