It would be great if we could push out tagged releases of this version of Beem rather than leave the 3+ year old abandoned version of Beem on Github as our "official" Python version.
When you try to edit a comment (top level post), you get an error "KeyError: 'parent_author'.
>>> comment.edit(new_body)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/mal/miniconda3/lib/python3.11/site-packages/beem/comment.py", line 748, in edit
original_post["parent_author"], original_post["parent_permlink"])
~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
File "/home/mal/miniconda3/lib/python3.11/site-packages/beem/blockchainobject.py", line 210, in __getitem__
return super(BlockchainObject, self).__getitem__(key)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
KeyError: 'parent_author'
Ultimately, Comment.edit() returns to a call to blockchaininstance.post() which I am able to use directly to work around this issue.
OS: Ubuntu 22.04 Hived Version: .3, .4, .5
I have been seeing this behavior recently on multiple geographically unique servers. This particular server has been running for over a year and using the same hived binary. One of our data centers had maintence that required taking the server offline. When brought backup it would spam these messages and nothing would happen.
I am using multiple good seed nodes and have verified ping connectivity as well as the ability to talk to them on port 2001.
974903ms p2p_plugin.cpp:466 plugin_startup ] P2P plugin startup...
974903ms chain_plugin.cpp:356 operator() ] Write processing thread started.
974932ms p2p_plugin.cpp:482 operator() ] Configuring P2P to listen at 0.0.0.0:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 51.161.87.119:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 188.165.235.19:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 104.26.6.217:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 104.26.7.217:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 172.67.73.79:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 188.114.97.3:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 188.114.96.3:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 116.202.160.108:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 91.183.35.138:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 51.222.244.100:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 65.21.199.174:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 195.201.172.94:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 65.21.235.184:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 116.202.168.187:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 88.99.165.91:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 78.46.81.76:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 95.217.203.90:2016
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 185.130.44.110:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 54.37.87.31:2001
974932ms p2p_plugin.cpp:490 operator() ] P2P adding seed node 173.249.42.156:2001
974932ms p2p_plugin.cpp:509 operator() ] Setting parameters
974933ms p2p_plugin.cpp:512 operator() ] Listening to P2P network
974933ms p2p_plugin.cpp:520 operator() ] Connection to P2P network
974933ms p2p_plugin.cpp:522 operator() ] Connected to P2P network
974933ms p2p_plugin.cpp:530 operator() ] P2P node listening at 0.0.0.0:2001
974933ms p2p_plugin.cpp:539 plugin_startup ] P2P Plugin started
974933ms witness_plugin.cpp:639 plugin_startup ] witness plugin: plugin_startup() begin
974933ms witness_plugin.cpp:652 plugin_startup ] Launching block production for 1 witness.
974933ms blockchain_worker_thread_pool.cpp:133 lazy_init ] Emplacing worker threads
974934ms blockchain_worker_thread_pool.cpp:145 lazy_init ] Emplacing worker threads done
974934ms witness_plugin.cpp:663 plugin_startup ] witness plugin: plugin_startup() end
Entering application main loop...
1004903ms chain_plugin.cpp:397 operator() ] No P2P data (block/transaction) received in last 30 seconds... peer_count=0
1034903ms chain_plugin.cpp:397 operator() ] No P2P data (block/transaction) received in last 30 seconds... peer_count=0
1064904ms chain_plugin.cpp:397 operator() ] No P2P data (block/transaction) received in last 30 seconds... peer_count=0
1094904ms chain_plugin.cpp:397 operator() ] No P2P data (block/transaction) received in last 30 seconds... peer_count=0
1124904ms chain_plugin.cpp:397 operator() ] No P2P data (block/transaction) received in last 30 seconds... peer_count=0
1154904ms chain_plugin.cpp:397 operator() ] No P2P data (block/transaction) received in last 30 seconds... peer_count=0
1184904ms chain_plugin.cpp:397 operator() ] No P2P data (block/transaction) received in last 30 seconds... peer_count=0
1214904ms chain_plugin.cpp:397 operator() ] No P2P data (block/transaction) received in last 30 seconds... peer_count=0
1244905ms chain_plugin.cpp:397 operator() ] No P2P data (block/transaction) received in last 30 seconds... peer_count=0
1274905ms chain_plugin.cpp:397 operator() ] No P2P data (block/transaction) received in last 30 seconds... peer_count=0
I have tried multiple reboots as well as rebuilding .3, .4 and .5 from source. The exact same result regardless, this is a known good machine that has been running for well over a year without issues. I saw the same behavior when building a new node also on Ubuntu 22.04 using the same process I have done 100 times.
I even went so far to reinstall a clean Ubuntu 22.04 and only ran the following commands.
sudo apt update
sudo apt upgrade
sudo reboot
git clone --recurse --branch master https://github.com/openhive-network/hive
sudo ./hive/scripts/setup_ubuntu.sh --dev
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release -GNinja ../hive
ninja hived cli_wallet -j8
sudo ninja install
hived --version
screen -S witness -L -Logfile witness.log
hived
I've even tried with rm -rf .hived and running no config.ini, using what it provides by default.
I looked through the peers.json log and all seeds show a similar result as this one.
{
"endpoint": "51.161.87.119:2001",
"last_seen_time": "1970-01-01T00:00:00",
"last_failed_time": "2023-11-08T08:33:05",
"last_connection_disposition": "last_connection_failed",
"last_connection_attempt_time": "2023-11-08T08:33:00",
"number_of_successful_connection_attempts": 0,
"number_of_failed_connection_attempts": 4,
"last_error": {
"code": 0,
"name": "exception",
"message": "unspecified",
"stack": [{
"context": {
"level": "warn",
"file": "node.cpp",
"line": 1493,
"method": "terminate_inactive_connections_loop",
"hostname": "",
"timestamp": "2023-11-08T08:33:05"
},
"format": "Terminating handshaking connection due to inactivity of ${timeout} seconds. Negotiating status: ${status}, bytes sent: ${sent}, bytes received: ${received}",
"data": {
"peer": "51.161.87.119:2001",
"timeout": 5,
"status": "connecting",
"sent": 0,
"received": 0
}
}
Yet, this particular one (seed.hive.blog) I have confirmed I can reach. So it isn't a network or firewall issue.
telnet seed.hive.blog 2001
Trying 51.161.87.119...
Connected to seed.hive.blog.
Escape character is '^]'.
��.�����/U~�S��&ytL���x\�1
I have seen this issue on 2-3 servers in the last couple of weeks all fresh Ubuntu 22.04 installs, with minimum install and configuration done. I also built the docker image, and had same result.
I'm not sure why this is all of a sudden happening, I've done this install a hundred times.
When creating a proposal, there is no transaction history of the fees involved. Many users are not aware of the costs for 61+ day proposal and there is no way to look on chain history to see what was spent on proposals. HBD just disappears from account with no trace.
A few users have mentioned issues with their reputation on Hive.blog. For example @glimpsytips reports 52 on Ecency and Peakd, but 5 on Hive.blog. Further research shows the API call is returning the inaccurate Reputation.
This is similar to the issue I noticed when reputation was disabled on Hivemind a while ago, certain things like the profile page would show one reputation but comments and posts would show another.
In this case, the user was flagged for testing notifications and his rep shows -2.
If you go to his profile, it shows 48 (on peakd).
But if you go to Hive.blog, it shows he is -3 rep.
Being below 10 rep disables features like image hosting and notification and disrupts UX it is also stressful for new users.
YouTube started a new category a while ago called YouTube Shorts, it is YouTube videos typically under 1 minute. While they are just normal YouTube videos, they do have a different URL syntax.
Example: https://www.youtube.com/shorts/bisADIYBdQM
Example Post: https://hive.blog/righttorepair/@theycallmemarky/best-explaination-of-right-to-repair
I suspect this should be an easy change to support YouTube Shorts Embeds.
Marky (64802f81) at 19 Sep 16:29
Greetings, We write on behalf of Coinbase to request your assistance based on the Evidence to mitigate harmful cyber activity, specifically customer support fraud at the Internet Presence Location using the inaccurate phone number identified above at the Internet Presence Location.
Similar to illegal robocalls coupled with misleading telephone numbers displayed as caller ID information, the Internet Presence Location is fraudulently masquerading as Coinbase in an attempt to wrongfully gain something of value from consumers. As part of this masquerade, the scammers are displaying an inaccurate phone number for Coinbase or Coinbase support at the Internet Presence Location, which based on the Evidence, is likely being used as part of a scammer phone network either in connection with illegal spoofing or a tech support scam. We are copying relevant authorities to investigate and take appropriate action based on the Evidence, and we ask for your support to take all reasonable and appropriate steps per your acceptable use policy before anyone is harmed.
Please also consider whether you may be able to replace the fraudulent masquerade at the Internet presence location with educational materials to protect consumers against illegal spoofing and fraudulent support scams.
Thank you for your support in this important consumer protection initiative.
Marky (64802f81) at 18 Sep 21:52
@samuel2009 phishing post