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

Error on Enabling Worker on 0.4.6 #210

Closed
lsji07 opened this issue Jun 15, 2018 · 4 comments · Fixed by #216
Closed

Error on Enabling Worker on 0.4.6 #210

lsji07 opened this issue Jun 15, 2018 · 4 comments · Fixed by #216

Comments

@lsji07
Copy link

lsji07 commented Jun 15, 2018

Expected Behavior

Running GUI and just downloaded new 0.4.6 version for win64.
On starting the existing worker (possibly workers if more used) was missing so I created a new worker with my strategy.
Expected it to operate as normal with my strategy.

Actual Behavior

Error message when activating worker as follows.

Traceback (most recent call last):
File "lib\site-packages\bitshares-0.1.16-py3.5.egg\bitsharesapi\bitsharesnoderpc.py", line 54, in rpcexec
File "lib\site-packages\graphenelib-0.6.1-py3.5.egg\grapheneapi\graphenewsrpc.py", line 173, in rpcexec
grapheneapi.exceptions.RPCError: irrelevant signature included: Unnecessary signature(s) detected

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "dexbot\worker.py", line 76, in init_workers
File "dexbot\strategies\staggered_orders.py", line 66, in init
File "dexbot\strategies\staggered_orders.py", line 127, in init_strategy
File "dexbot\basestrategy.py", line 436, in market_buy
File "dexbot\basestrategy.py", line 580, in retry_action
File "lib\site-packages\bitshares-0.1.16-py3.5.egg\bitshares\market.py", line 432, in buy
File "lib\site-packages\bitshares-0.1.16-py3.5.egg\bitshares\bitshares.py", line 282, in finalizeOp

Steps to Reproduce the Problem

  1. Run new version
  2. Setup new worker.
  3. Error message...

Specifications

  • Version: 0.4.6. Previous version running stable was 0.4.0
  • OS: Win 64 Pro
@MarkoPaasila
Copy link
Collaborator

You probably have duplicate keys in uptick. It will be fixed in the future but we just have to wait. In the meantime you will have to find the uptick wallet file and remove it. Then start fresh. See "common problems" in the wiki.

@lsji07
Copy link
Author

lsji07 commented Jun 18, 2018

Thanks, This sorted my issue out.

@kohako
Copy link

kohako commented Jun 30, 2018

where is the uptick wallet file located ?

@mikakoi
Copy link
Collaborator

mikakoi commented Jul 17, 2018

@kohako check the wiki, the file is called bitshares.sqlite

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants