-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
RSS Import: Issue with KeyError: 'cw' #126
Comments
Hi! pleroma-bot --version The latest release candidate as of now for the bot is
I'm wondering if it still happening on |
That was on 1.2.0. When I updated it, I got a different error instead during the posting part:
Which was very similar to the error I got when I commented out the cw line in the previous version. |
Does it make any difference if you clean up the temp folder |
It looks like clearing out the tweets folder fixed it, I guess running it previously caused something to get stuck in the tweets that shouldn't have been there. Now I just have an issue where it's not pulling old tweets that were made when the bot wasn't functioning properly and posting them, but that's a separate issue. |
This happens because some fields are called even if they can be undefined. It could be fixed by making sure those fields are always initialised or by checking before reference. (Small example patch incoming.) |
Can happen with RSS input. Addresses issue robertoszek#126
Having a small issue where the bot will collect tweets while using RSS, but will fail to post because of the following error:
✖ 2023-03-19 13:45:58,341 - pleroma_bot - ERROR - Exception occurred for user, skipping... (cli.py:717) Traceback (most recent call last): File "/usr/local/lib/python3.10/dist-packages/pleroma_bot/cli.py", line 695, in main cw=tweet["cw"] KeyError: 'cw'
Commenting out that section lets it post a few times, but then it stops because of a number of other issues in a series of other lines which I didn't want to mess around with in case it broke further.
The text was updated successfully, but these errors were encountered: