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

There is no entry with the name 'BURN' in your exchange account #29

Open
asmodehn opened this issue Jun 28, 2019 · 2 comments
Open

There is no entry with the name 'BURN' in your exchange account #29

asmodehn opened this issue Jun 28, 2019 · 2 comments
Labels
bug Something isn't working

Comments

@asmodehn
Copy link
Contributor

After Initializing my ledgers (for kraken and bitstamp), running the dashboard, and then visiting the fees and assets pages, I get :

INFO:root:200 GET /fees (127.0.0.1) 13.96ms - FAST
/home/alexv/.virtualenvs/gryphon2/local/lib/python2.7/site-packages/sqlalchemy/sql/sqltypes.py:242: SAWarning: Unicode type received non-unicode bind param value 'DEPOSIT'. (this warning may be suppressed after 10 occurrences)
  (util.ellipses_string(value),))
/home/alexv/.virtualenvs/gryphon2/local/lib/python2.7/site-packages/sqlalchemy/sql/sqltypes.py:242: SAWarning: Unicode type received non-unicode bind param value 'WITHDRAWL'. (this warning may be suppressed after 10 occurrences)
  (util.ellipses_string(value),))
/home/alexv/.virtualenvs/gryphon2/local/lib/python2.7/site-packages/sqlalchemy/sql/sqltypes.py:242: SAWarning: Unicode type received non-unicode bind param value 'BURN'. (this warning may be suppressed after 10 occurrences)
  (util.ellipses_string(value),))
INFO:gryphon.lib.assets:There is no entry with the name 'BURN' in your exchange account table, so we won'tbe able to show non-trading expenses in the dashboard service. You can learn how toset this feature up in the framework documentation.
INFO:root:200 GET /assets (127.0.0.1) 596.35ms - SLOW
  1. There should probably be a link to the correct section in the documentation ? I m guessing it might be the ledger initialization part, but I might be wrong ?

  2. How can I check if it is a problem in code or in DB setup ?

@garethdmm
Copy link
Owner

garethdmm commented Jun 28, 2019

Will take a look at this shortly.

@garethdmm garethdmm added the bug Something isn't working label Jul 2, 2019
@tdudz
Copy link

tdudz commented Sep 1, 2019

i am getting this same output to the log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants