-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Feat / candle feed from Coinbase Advanced Trade v2.1 #6889
base: development
Are you sure you want to change the base?
Feat / candle feed from Coinbase Advanced Trade v2.1 #6889
Conversation
Hey @MementoRC, just a reminder this PR and also #6888 is pointing to |
@david-hummingbot thank you. corrected |
Locally, I get:
|
@david-hummingbot The |
2 similar comments
PR update:
|
|
@rapcmia The 429 error could be a temporary issue, the candles uses the time_synchronizer, which itself is controlled by the rate limit of the /time endpoint - note that it is not a rate limit error and could come from intermediate server when the bot send the http request (maybe a cloud server this go/sg/... is odd) The candle feed only has the 5mn websocket feed on Coinbase, all other intervals are done with a custom REST call, I'd need a bit of time to get back into what was implemented, the repeating entries could be a mismatch between strat/end of each looped request |
@rapcmia I think I found a bug: for each REST request the end_time was incorrectly set |
PR update on commit
|
|
@rapcmia ok, only the websocket changes (the |
@rapcmia Silly mistake, I tried to re-use the historical fill method, but it is shielded by the self.ready() and thus never get the latest candles. I separated the REST call and now it seems to be fixed. Thank you |
Before submitting this PR, please make sure:
A description of the changes proposed in the pull request:
Candle feed from Coinbase Advanced Trade
Tests performed by the developer:
ran tests in select coinbase spot_candles
Tips for QA testing: