rapcmia / hummingbot Goto Github PK

View Code? Open in Web Editor NEW

This project forked from hummingbot/hummingbot

0.0 0.0 0.0 528.58 MB

Hummingbot: a client for crypto market making

Home Page: https://www.hummingbot.io/

License: Apache License 2.0

Python 91.49% Shell 0.03% Batchfile 0.01% Dockerfile 0.04% C++ 0.16% Makefile 0.01% Cython 8.27%

hummingbot's People

Contributors

hummingbot's Issues

Describe the bug

asdasd

Steps to reproduce

Release version

asd

Type of installation

Source

Attach required files

No response

test 3

Describe the bug
// A clear and concise description of what the bug is.

Steps To Reproduce
// A concise description of the steps to reproduce the buggy behavior:

Here are the steps to reproduce the issue (see attachments in the section below):

Set up your configuration file with these parameters: ...
Start the bot using this command: ...
...

Screenshots
// If applicable, add screenshots to help explain your problem.

Release version
// Include your bot's version number (Can be found at the upper left corner of your CLI).

Attachments
// Please attach your config file and log file to help us debug. It would be difficult for us to help you without those!

WARNING: Do NOT publish any exchange API keys or your wallet's private key. Whoever has access to them may steal your assets!

Optional: your discord username:

test 2

Describe the bug
// A clear and concise description of what the bug is.

Steps To Reproduce
// A concise description of the steps to reproduce the buggy behavior:

Here are the steps to reproduce the issue (see attachments in the section below):

Set up your configuration file with these parameters: ...
Start the bot using this command: ...
...

Screenshots
// If applicable, add screenshots to help explain your problem.

Release version
// Include your bot's version number (Can be found at the upper left corner of your CLI).

Attachments
// Please attach your config file and log file to help us debug. It would be difficult for us to help you without those!

WARNING: Do NOT publish any exchange API keys or your wallet's private key. Whoever has access to them may steal your assets!

Optional: your discord username:

Describe the bug

While checking development branch, We noticed these Error getting server time. and There was an error requesting exchange info. for foxbit connector

2023-05-17 10:09:15,158 - 8058 - hummingbot.connector.time_synchronizer - NETWORK - Error getting server time.
Traceback (most recent call last):
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/time_synchronizer.py", line 65, in update_server_time_offset_with_time_provider
    server_time_ms: float = await time_provider
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange/foxbit/foxbit_web_utils.py", line 98, in get_current_server_time
    response = await rest_assistant.execute_request(url=public_rest_url(path_url=CONSTANTS.SERVER_TIME_PATH_URL,
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/core/web_assistant/rest_assistant.py", line 75, in execute_request
    raise IOError(f"Error executing request {method.name} {url}. HTTP status is {response.status}. "
OSError: Error executing request GET https://api.foxbit.com.br/rest/v3/system/time. HTTP status is 503. Error: N/A
2023-05-17 10:09:15,159 - 8058 - hummingbot.connector.time_synchronizer - WARNING - Could not refresh server time. Check network connection.
2023-05-17 10:09:15,971 - 8058 - hummingbot.connector.exchange.foxbit.foxbit_exchange.FoxbitExchange - ERROR - There was an error requesting exchange info.
Traceback (most recent call last):
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange_py_base.py", line 1088, in _initialize_trading_pair_symbol_map
    exchange_info = await self._make_trading_pairs_request()
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange_py_base.py", line 1101, in _make_trading_pairs_request
    exchange_info = await self._api_get(path_url=self.trading_pairs_request_path)
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange_py_base.py", line 892, in _api_get
    return await self._api_request(*args, **kwargs)
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange_py_base.py", line 934, in _api_request
    request_result = await rest_assistant.execute_request(
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/core/web_assistant/rest_assistant.py", line 75, in execute_request
    raise IOError(f"Error executing request {method.name} {url}. HTTP status is {response.status}. "
OSError: Error executing request GET https://api.foxbit.com.br/rest/v3/markets. HTTP status is 503. Error: N/A

Note: This error does not affect other connectors and client performance. For monitoring purpose

Steps to reproduce

Setup latest development branch for client
Start the client and observe the log panel

Release version

dev-1.16.0

Type of installation

Source

Attach required files

logs_pmm-binance1.log

Describe the bug

Bug happened OMG please fix it, thank you

Steps to reproduce

Start the app
connect exchange
It fails to connect
I'm sad

Release version

1.100

Type of installation

Source

Attach required files

I don't know where is the files :(((

Discord name

No response

Describe the bug

testst

Steps to reproduce

asd

Release version

asd

Type of installation

Source

Attach required files

asd

test webhook

Describe the bug
// A clear and concise description of what the bug is.

Steps To Reproduce
// A concise description of the steps to reproduce the buggy behavior:

Here are the steps to reproduce the issue (see attachments in the section below):

Set up your configuration file with these parameters: ...
Start the bot using this command: ...
...

Screenshots
// If applicable, add screenshots to help explain your problem.

Release version
// Include your bot's version number (Can be found at the upper left corner of your CLI).

Attachments
// Please attach your config file and log file to help us debug. It would be difficult for us to help you without those!

WARNING: Do NOT publish any exchange API keys or your wallet's private key. Whoever has access to them may steal your assets!

Optional: your discord username:

test 1

Describe the bug
// A clear and concise description of what the bug is.

Steps To Reproduce
// A concise description of the steps to reproduce the buggy behavior:

Here are the steps to reproduce the issue (see attachments in the section below):

Set up your configuration file with these parameters: ...
Start the bot using this command: ...
...

Screenshots
// If applicable, add screenshots to help explain your problem.

Release version
// Include your bot's version number (Can be found at the upper left corner of your CLI).

Attachments
// Please attach your config file and log file to help us debug. It would be difficult for us to help you without those!

WARNING: Do NOT publish any exchange API keys or your wallet's private key. Whoever has access to them may steal your assets!

Optional: your discord username:

Describe the bug

asd

Steps to reproduce

Release version

Type of installation

Source

Attach required files

123123123

Discord name

No response

Describe the bug

While checking development branch, We noticed these Error getting server time. and There was an error requesting exchange info. for foxbit connector

2023-05-17 10:09:15,158 - 8058 - hummingbot.connector.time_synchronizer - NETWORK - Error getting server time.
Traceback (most recent call last):
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/time_synchronizer.py", line 65, in update_server_time_offset_with_time_provider
    server_time_ms: float = await time_provider
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange/foxbit/foxbit_web_utils.py", line 98, in get_current_server_time
    response = await rest_assistant.execute_request(url=public_rest_url(path_url=CONSTANTS.SERVER_TIME_PATH_URL,
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/core/web_assistant/rest_assistant.py", line 75, in execute_request
    raise IOError(f"Error executing request {method.name} {url}. HTTP status is {response.status}. "
OSError: Error executing request GET https://api.foxbit.com.br/rest/v3/system/time. HTTP status is 503. Error: N/A
2023-05-17 10:09:15,159 - 8058 - hummingbot.connector.time_synchronizer - WARNING - Could not refresh server time. Check network connection.
2023-05-17 10:09:15,971 - 8058 - hummingbot.connector.exchange.foxbit.foxbit_exchange.FoxbitExchange - ERROR - There was an error requesting exchange info.
Traceback (most recent call last):
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange_py_base.py", line 1088, in _initialize_trading_pair_symbol_map
    exchange_info = await self._make_trading_pairs_request()
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange_py_base.py", line 1101, in _make_trading_pairs_request
    exchange_info = await self._api_get(path_url=self.trading_pairs_request_path)
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange_py_base.py", line 892, in _api_get
    return await self._api_request(*args, **kwargs)
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange_py_base.py", line 934, in _api_request
    request_result = await rest_assistant.execute_request(
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/core/web_assistant/rest_assistant.py", line 75, in execute_request
    raise IOError(f"Error executing request {method.name} {url}. HTTP status is {response.status}. "
OSError: Error executing request GET https://api.foxbit.com.br/rest/v3/markets. HTTP status is 503. Error: N/A

Note: This error does not affect other connectors and client performance. For monitoring purpose

Steps to reproduce

Setup latest development branch for client
Start the client and observe the log panel

Release version

123

Type of installation

Source

Attach required files

logs_hummingbot.log

Certificate path becomes configurable

Feature Suggestion

The certs used to connect to the gateway are now fixed on the client side. Because they certs are fixed, multiple clients cannot connect to one gateway. The client now can only connect to the gateway that uses the certs it generates.

To change this, we need to make the path for the certs used by the client a configurable one.

Path become part of the client global conf.
Path is updated when using gateway generate-certs to that client's own certs.
Path can be updated using new command config certs.path

Impact

This will allow users to use and reuse certs.
This will allow multiple clients to connect to a single gateway.
Path will be updated automatically when running gateway generate-certs

Additional context

No response

Bounty request

Description

A new Candles Feed for Gate.io Spot and Perpetuals
Should implement the CandlesBase class like the Binance candles.
Support web sockets to stream new messages and rest to collect historical data
Contains unit tests and meets % coverage requirements
You can find the candles feed inside hummingbot/data_feed/candles_feed

Bounty

Sponsor: Ralph Comia
Bounty amount: 10,000 HBOT
Developer portion: 100%

Bug Report

Describe the bug

asd

Steps to reproduce

asd

Release version

asd

Type of installation

Source

Attach required files

asd

Discord name

No response

Bug Report

Describe the bug

While checking development branch, We noticed these Error getting server time. and There was an error requesting exchange info. for foxbit connector

2023-05-17 10:09:15,158 - 8058 - hummingbot.connector.time_synchronizer - NETWORK - Error getting server time.
Traceback (most recent call last):
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/time_synchronizer.py", line 65, in update_server_time_offset_with_time_provider
    server_time_ms: float = await time_provider
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange/foxbit/foxbit_web_utils.py", line 98, in get_current_server_time
    response = await rest_assistant.execute_request(url=public_rest_url(path_url=CONSTANTS.SERVER_TIME_PATH_URL,
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/core/web_assistant/rest_assistant.py", line 75, in execute_request
    raise IOError(f"Error executing request {method.name} {url}. HTTP status is {response.status}. "
OSError: Error executing request GET https://api.foxbit.com.br/rest/v3/system/time. HTTP status is 503. Error: N/A
2023-05-17 10:09:15,159 - 8058 - hummingbot.connector.time_synchronizer - WARNING - Could not refresh server time. Check network connection.
2023-05-17 10:09:15,971 - 8058 - hummingbot.connector.exchange.foxbit.foxbit_exchange.FoxbitExchange - ERROR - There was an error requesting exchange info.
Traceback (most recent call last):
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange_py_base.py", line 1088, in _initialize_trading_pair_symbol_map
    exchange_info = await self._make_trading_pairs_request()
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange_py_base.py", line 1101, in _make_trading_pairs_request
    exchange_info = await self._api_get(path_url=self.trading_pairs_request_path)
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange_py_base.py", line 892, in _api_get
    return await self._api_request(*args, **kwargs)
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/connector/exchange_py_base.py", line 934, in _api_request
    request_result = await rest_assistant.execute_request(
  File "/home/rapcmia/github/hummingbot/dev/hummingbot/core/web_assistant/rest_assistant.py", line 75, in execute_request
    raise IOError(f"Error executing request {method.name} {url}. HTTP status is {response.status}. "
OSError: Error executing request GET https://api.foxbit.com.br/rest/v3/markets. HTTP status is 503. Error: N/A

Note: This error does not affect other connectors and client performance. For monitoring purpose

Steps to reproduce

Setup latest development branch for client
Start the client and observe the log panel

Release version

dev 1.16.0

Type of installation

Source

Attach required files

logs_hummingbot.log

test

Description

test

Reproduction URL

test

Reproduction steps

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots

![DESCRIPTION](LINK.png)

Logs

2023-05-23 19:59:09,182 - 7520 - hummingbot.client.hummingbot_application - INFO - Creating the clock with tick size: 1.0
2023-05-23 19:59:09,184 - 7520 - hummingbot.client.hummingbot_application - INFO - start command initiated.
2023-05-23 19:59:09,509 - 7520 - hummingbot.connector.exchange.binance.binance_exchange.BinanceExchange - INFO - Network status has changed to NetworkStatus.CONNECTED. Starting networking...
2023-05-23 19:59:09,838 - 7520 - hummingbot.connector.exchange.binance.binance_api_user_stream_data_source.BinanceAPIUserStreamDataSource - INFO - Successfully obtained listen key hGgSTNKxWWg911fQI6ZakmjNnxKv8iculPklLC3gEcUr6ijBOBkk62odOFMr
2023-05-23 19:59:10,026 - 7520 - hummingbot.core.data_type.order_book_tracker - INFO - Initialized order book for XRP-USDT. 1/1 completed.
2023-05-23 19:59:10,325 - 7520 - hummingbot.connector.exchange.binance.binance_api_order_book_data_source.BinanceAPIOrderBookDataSource - INFO - Subscribed to public order book and trade channels...
2023-05-23 19:59:12,001 - 7520 - hummingbot.strategy.pure_market_making.pure_market_making - INFO - (XRP-USDT) Creating 1 bid orders at (Size, Price): ['25 XRP, 0.4562 USDT']
2023-05-23 19:59:12,284 - 7520 - hummingbot.connector.client_order_tracker - INFO - Created LIMIT_MAKER BUY order x-XEKWYICXBXPUT5fc5b1d93caadc345 for 25.00000000 XRP-USDT.
2023-05-23 19:59:12,301 - 7520 - hummingbot.core.event.event_reporter - EVENT_LOG - {"timestamp": 1684843152.0, "type": "OrderType.LIMIT_MAKER", "trading_pair": "XRP-USDT", "amount": "25.00000000", "price": "0.45620000", "order_id": "x-XEKWYICXBXPUT5fc5b1d93caadc345", "creation_timestamp": 1684843152.0, "exchange_order_id": "5193300449", "leverage": 1, "position": "NIL", "event_name": "BuyOrderCreatedEvent", "event_source": "binance"}
2023-05-23 19:59:13,553 - 7520 - hummingbot.core.rate_oracle.rate_oracle - INFO - Network status has changed to NetworkStatus.CONNECTED. Starting networking...
2023-05-23 19:59:32,452 - 7520 - hummingbot.client.hummingbot_application - INFO - stop command initiated.
2023-05-23 19:59:32,684 - 7520 - hummingbot.core.event.event_reporter - EVENT_LOG - {"timestamp": 1684843172.0, "order_id": "x-XEKWYICXBXPUT5fc5b1d93caadc345", "exchange_order_id": "5193300449", "event_name": "OrderCancelledEvent", "event_source": "binance"}
2023-05-23 19:59:32,685 - 7520 - hummingbot.connector.client_order_tracker - INFO - Successfully canceled order x-XEKWYICXBXPUT5fc5b1d93caadc345.
2023-05-23 19:59:34,344 - 7520 - hummingbot.client.hummingbot_application - INFO - Creating the clock with tick size: 1.0
2023-05-23 19:59:34,345 - 7520 - hummingbot.client.hummingbot_application - INFO - start command initiated.
2023-05-23 19:59:34,567 - 7520 - hummingbot.connector.exchange.binance.binance_exchange.BinanceExchange - INFO - Network status has changed to NetworkStatus.CONNECTED. Starting networking...
2023-05-23 19:59:34,719 - 7520 - hummingbot.connector.exchange.binance.binance_api_user_stream_data_source.BinanceAPIUserStreamDataSource - INFO - Successfully obtained listen key hGgSTNKxWWg911fQI6ZakmjNnxKv8iculPklLC3gEcUr6ijBOBkk62odOFMr

Browsers

No response

OS

No response

Bug Report

Describe the bug

asd

Steps to reproduce

Release version

asd

Type of installation

Source

Attach required files

No response

rapcmia / hummingbot Goto Github PK

hummingbot's People

Contributors

hummingbot's Issues

Describe the bug

Steps to reproduce

Release version

Type of installation

Attach required files

Describe the bug

Steps to reproduce

Release version

Type of installation

Attach required files

Describe the bug

Steps to reproduce

Release version

Type of installation

Attach required files

Discord name

Describe the bug

Steps to reproduce

Release version

Type of installation

Attach required files

Describe the bug

Steps to reproduce

Release version

Type of installation

Attach required files

Discord name

Describe the bug

Steps to reproduce

Release version

Type of installation

Attach required files

Feature Suggestion

Impact

Additional context

Description

Bounty

Describe the bug

Steps to reproduce

Release version

Type of installation

Attach required files

Discord name

Describe the bug

Steps to reproduce

Release version

Type of installation

Attach required files

Description

Reproduction URL

Reproduction steps

Screenshots

Logs

Browsers

OS

Describe the bug

Steps to reproduce

Release version

Type of installation

Attach required files

Recommend Projects

Recommend Topics

Recommend Org