This repository has been archived by the owner on Feb 16, 2020. It is now read-only.
0.5.11 #1451
Merged
0.5.11 #1451
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Not yet functional
Though slightly less performant, this option is the most compatible across operating systems, so it really ought to be the default.
Support for Binance Exchange, including Import
Normally commands for Bots on Telegram start with a `/`: https://core.telegram.org/bots#commands
Fixed the 520 code Added 504 and 502 as these also happen with Kraken's recent issues (and are retryable)
Normalize "err" field as "undefined" when there is no error
Fix various issues with SQLITE 3 and import task shutdown
* Fix node-postgres version to 6.1.0 on Dockerfile Refs #1041 * Fixed spelling of names
* Make the Dockerfile leaner Batching commands to reduce layers, adding npm clean and using --production flag reduces final docker image by about 100 MB (860MB -> 760MB) * Remove an outdated comment
* Fix node-postgres version to 6.1.0 on Dockerfile Refs #1041 * Fix sharpe ratio formula
Now everyone using this tool will have consistent settings automatically.
* Fix a few unlikely issues with empty trade iterations (Binance) * Fix getProtfolio function in Binance * Fixing getPortfolio in binance * Fix getTicker * Add timestamp to newOrder query Normally the binance api module adds this automatically for requests that require it, but it is not on newOrder. Probably an oversight, but an easy workaround on our side. * Clean up markets, correct min amounts * Staged the wrong file :S * Rounding amount and price accoring to their designated precision * Fix nasty copy and paste error
…rrors (#1427) * Fix a few unlikely issues with empty trade iterations (Binance) * Fix getProtfolio function in Binance * Fixing getPortfolio in binance * Fix getTicker * Add timestamp to newOrder query Normally the binance api module adds this automatically for requests that require it, but it is not on newOrder. Probably an oversight, but an easy workaround on our side. * Clean up markets, correct min amounts * Staged the wrong file :S * Rounding amount and price accoring to their designated precision * Fix nasty copy and paste error * Fix rounding errors of small amounts * Typo fix
* Fix node-postgres version to 6.1.0 on Dockerfile Refs #1041 * docs: fixed spelling error in introduction "build in" to "built-in"
* Experimenting with a new pattern * Moving retry handler into the exchange * Bugfixes, and retry handling appears to work great now * g/process/processResult/ * remove missing reqData * remove always recoverable * propogate the last error, not the first * make handleResponse higher order
* fix ppo result for api exposure * fix tests * fix tests
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Minor release with a focus on stabilising exchange API consumption.
NOTE: even though this is a minor release, there is a breaking change in the API of the PPO indicator, if you are using it in a strategy please refer here for changes: #1443.