-
Notifications
You must be signed in to change notification settings - Fork 40
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
Added resteem functionality to Responder #18
base: master
Are you sure you want to change the base?
Conversation
Thank you very much. I will test it soon by the meantime can you please change your indention from tabs to 2 space which is the convention for this codebase. |
Thats bonkers.
I swear it was spaces pre-commit, I guess I misconfigured VIM.
…On Mon, Apr 16, 2018, 8:12 AM p0o ***@***.***> wrote:
Thank you very much. I will test it soon by the meantime can you please
change your indention from tabs to 2 space which is the convention for this
codebase.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#18 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AVm2rQQAP1AvcP5iJ5Q9cOi9MQZQU085ks5tpDY8gaJpZM4TVkVb>
.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are some issues with the code, I tried debugging it for a short period but even with fixing these issues the bot is not resteeming. Not sure what is the problem maybe you test yourself and check.
const wif = this.postingKey || this.activeKey; | ||
|
||
const action = JSON.stringify(['reblog'], { | ||
account: this.responserUsername, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo in "responder"
wif, | ||
[], | ||
[this.responderUsername], | ||
'follow', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the id for transaction is "follow" ? I don't remember exactly but I think it should be a random string like a uuid. since the new commit in node from the second execution it returns this error:
Unhandled rejection RPCError: Assert Exception:_callbacks.find( txid ) == _callbacks.end(): Transaction is a duplicate
at new RPCError (/Users/p0o/dev/steem-bot-tests/steem-bot/node_modules/steem/lib/api/transports/http.js:39:106)
at /Users/p0o/dev/steem-bot-tests/steem-bot/node_modules/steem/lib/api/transports/http.js:74:13
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
@TwinkieWInkie Hey, you still want to finish this? |
Untested as of now, not expecting any errors as the implementation is correct.
close #6