Uh oh!
There was an error while loading. Please reload this page.
fix installation - #48
Open
gorazdko wants to merge 4 commits into
Open
Conversation
gorazdko
commented
Jan 7, 2021
Author
cc: @shannona |
ChristopherA
commented
Jan 7, 2021
Contributor
Is this version live at our public onion? Or only tested on your personal copy? |
gorazdko
commented
Jan 7, 2021
Author
only on a personal copy. Don't have login credentials of our public onion yet |
This file contains hidden or 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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Abstract
This PR fixes#47
and possibly the memory issues reported in #45EDIT: just tested tested on our live version debian 10 - the logs there are properly capped, but they weren't on a ubuntu machine with 1GB RAM which I tested on. So it doesnt solve #45, logs are saying DB locked
Status
WIP:
http://orq3s6o3j3oudmczjmh4yxuihnblh2lro6rvjdhixnhgguitidlsbyyd.onion/hist/USD/bitstamp/1610057000/1610057865throws empty data. I'll have to check if downgradingccxtfixes this