BLUF
Means "Bottom Line Up Front" for the Uninitiated
This issue is currently causing an interruption in the functionality of the @steemflagrewards bot due to Type Errors experienced with get_blog().
It is possible that the issue issue is related to the Steem RPC node API and not exclusively Beem but, nevertheless, this is the symptom and will require more advanced troubleshooting to isolate.
I can "band-aid" the issue by removing the get_blog() method invocation on our status command and report posting functionality but this will result in our bot being unable to regulate it's posting frequency which is less than ideal with the number of distinct flaggers we go through daily. Our current posting threshold is 9 distinct flaggers which, when there is a lot of abuse on the horizon, we can hit in a matter of 30 minutes.
We have had a drastic increase of flaggers via functionality our friend @reazuliqbal has provided with his flag trail which is an extremely useful tool he has provided along with repository as well as the Discord server and bot he maintains. This trail results in our rapidly hitting the flagger threshold and removing rewards from Steem abuse. after flags have been properly vetted and approved by our mods.
Isn't it glorious?
I did want to use this post as an opportunity to point out that the flag trail submission is a severely undervalued post and ask the community to please take a look at give a second opinion to @codingdefined's review which, in my humble opinion was a horrible job as he commented favorably but scored the contribution low without constructive feedback. If there was ever a @utopian-io moderator review I would flag, this one is it. I made sure to let him know while I was at it. @knowledges said he would work to correct this but we're at the 5th day of the post; therefore, I am now making my appeal to the community for enhanced curation.
I was much more fond of @pjau's alternative review.
With that, let's get back to the bug report...
Project Information
Repository: https://github.com/holgern/beem
Project Name: Beem
Publisher (if applicable): @holger80
Expected behavior
The following line would obtain the account's last main post.
post = sfr.get_blog(limit=1)[0]
Which is used by the @steemflagrewards to implement our posting frequency limit (1 report / 4 hours) and status command containing link to last report. Both are non-functional as a result.
It has been working up until earlier today. I've successfully ensured the library was up to date but issue persists.
Actual behavior
How to reproduce
You may reproduce the bug interactively as follows:
from beem import Steem
from beem.account import Account
from beem.comment import Comment
stm = Steem(nodes='')
sfr = Account('steemflagrewards', steem_instance=stm)
post = sfr.get_blog(limit=1)[0]
Which results in error as follows:
Traceback (most recent call last):
File "", line 1, in
File "/home/sfr/miniconda3/lib/python3.6/site-packages/beem/account.py", line 738, in get_blog
Comment(c["comment"], steem_instance=self.steem) for c in self.steem.rpc.get_blog({'account': account, 'start_entry_id': start_entry_id, 'limit': limit}, api='follow')["blog"]
TypeError: list indices must be integers or slices, not str
Browser/App version: Beem version 0.20.16
Operating system: Ubuntu 18.04.1 LTS
Recording Of The Bug
GitHub Account
https://github.com/anthonyadavisii
Nodes attempted
-https://api.steemit.com
-https://gtg.steem.house:8090
-https://anyx.io
Would you like to delegate to the Steem Flag Rewards project and promote decentralized moderation? It's much more fashionabe than self-voting. Here are some handy delegation links!
Last but not Least
Please, consider following the @sfr-mod-fund Fanbase on SteemAuto to support the activity of our 9 moderators regularly reviewing and approving legitimate community flags. It's your support that keeps the ball rolling and I greatly appreciate it!
Steem Cop Signing Out
When you get the off-brand idubbbz but for the Steem Blockchain, you get...
