Replies: 3 comments 3 replies
-
birdnet/lib64/python3.9/site-packages/apprise/AppriseAsset.py does not initialise plugin_paths
In my other installation (which I have not updated today) plugin_paths is initialised in birdnet/lib64/python3.9/site-packages/apprise/AppriseAsset.py
|
Beta Was this translation helpful? Give feedback.
-
I'm sorry about this - I committed some code to the repo which seems to have broken things. I've reverted the change so an update should bring your installation back to a working state. (Although I see you've already reinstalled.) |
Beta Was this translation helpful? Give feedback.
-
If you don't mind, I'm just observing this, but if there is a way i can add more bulletproofing to Apprise, let me know. Was the plugin path added pointing back to a large library? I'm trying to understand what it tried to load under the hood in this case |
Beta Was this translation helpful? Give feedback.
-
Just updated and update hung for several minutes. Rebooted and seeing this in the log:
11:03:48---Traceback (most recent call last):
11:03:48--- File "/usr/local/bin/server.py", line 16, in
11:03:48--- from utils.notifications import sendAppriseNotifications
11:03:48--- File "BirdNET-Pi/scripts/utils/notifications.py", line 16, in
11:03:48--- asset = apprise.AppriseAsset(
11:03:48--- File "BirdNET-Pi/birdnet/lib/python3.9/site-packages/apprise/AppriseAsset.py", line 157, in init
11:03:48--- raise AttributeError(
11:03:48---AttributeError: AppriseAsset init(): An invalid key plugin_paths was specified.
In the code tab I see notifications.py "Merge pull request #724 [from knmurphy/enable-apprise-plugins
That has
asset = apprise.AppriseAsset(
plugin_paths=[
userDir + "/.apprise/plugins",
userDir + "/.config/apprise/plugins",
]
)
I have no .apprise directory on my system. I do have .config but it does not have an apprise subdirectory
Beta Was this translation helpful? Give feedback.
All reactions