You are viewing a single comment's thread from:

RE: TypeError on getblog via Beem - Multiple Nodes Tested

in #utopian-io5 years ago

Hi @anthonyadavisii,
I was asked to also review this post as Utopian bug report. I was in contact with Holger and he confirmed that, despite being related to the changes to the Steemit node, the node output could be handled in beem, therefore accepting it as a bug report for beem. Your post contains a lot of SFR background information on how you use this functionality. This is not directly related to the bug report, but I assume this is meant to provide context to the readers. It has become common practice to include the version number in the title, but I'd consider this a minor detail. The steps to trigger the error are (beside the small typo mentioned in my other comment) clear and allow the maintainer to reproduce the issue. Thanks for your report!

Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.

To view those questions and the relevant answers related to your post, click here.

PS: I personally strongly dislike the call for flags on the mod review at this place. I hear your position and don't have a full picture myself, but I saw this issue is being discussed in length on Discord.


Need help? Write a ticket on https://support.utopian.io/.
Chat with us on Discord.
[utopian-moderator]

Sort:  

Thanks, @crokkon. Will take note of the version number and try to stick to more essential information.

the node output could be handled in beem

So, you're saying the key error was related to something other than a disabled plug-in? Perhaps, something transient?

PS: I personally strongly dislike the call for flags on the mod review at this place. I hear your position and don't have a full picture myself, but I saw this issue is being discussed in length on Discord.

Yes, I admit I went overboard but am still conflicted on the apparent precedent of not flagging a mod comment for disagreement of rewards. There were a few aggravating factors which earnestly caused me to believe his review was not worth it's pending payout.

After this ordeal, I do not plan on ever flagging a mod comment again even if I think it may be overvalued as I have learned the correct process of submitting a ticket for such issues.

In any case, I think mods should make a reasonable effort to leave meaningful and contructive feedback especially if they are going to give something critical score as otherwise it seems hypocritical.

I'll work on being more tactful and patient. Thank you.

So, you're saying the key error was related to something other than a disabled plug-in? Perhaps, something transient?

beem was primarily designed to talk to a steemd daemon, directly via wss or proxied via https. What Steemit did recently, was to replace the steemd daemon behind api.steemit.com with a hivemind instance, which has partly identical, partly similar and partly completely different output compared to steemd. get_blog is not officially ported to hivemind and Steemit makes no guarantees on the availability of this call. Currently, the output is at least different than on a steemd instance, which made beem fail with the type error you discovered.

Coin Marketplace

STEEM 0.29
TRX 0.12
JST 0.032
BTC 63572.52
ETH 3097.69
USDT 1.00
SBD 3.88