You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When loading a plugin that is not one of the "core" plugins causes an error, that error is not output to the log. Instead a somewhat generic error is logged, that can also be misleading because it refers to "core" plugins explicitly:
webapp | WARNING Failed to instantiate plugin example: No module named 'coreplugins.example'
What would be better
webapp | WARNING Failed to instantiate plugin example: No module named 'coreplugins.example': whatever the error was during previous attempts to load the plugin, if any
Make sure that plugin raises some exception, e.g. by adding raise BaseException("something went awfully wrong") in the __init__.py file of the plugin.
Restart WebODM
Look for Failed to instantiate plugin example: No module named 'coreplugins.example' and observe how nothing around tells you that something went awfully wrong. (Maybe wonder for a bit why coreplugins was involved, but that's a separate topic. 🙂)
Additional context
I came across this when trying to figure out if a cv2 import error was fixed in the context of this forum thread.
The text was updated successfully, but these errors were encountered:
How did you install WebODM?
Docker, but it's not relevant to the issue.
What's your browser and operating system?
Not relevant to the issue.
What is the problem?
What happens
When loading a plugin that is not one of the "core" plugins causes an error, that error is not output to the log. Instead a somewhat generic error is logged, that can also be misleading because it refers to "core" plugins explicitly:
What would be better
Relevant code
How can we reproduce this?
MEDIA_DIR/plugins
, sayexample
raise BaseException("something went awfully wrong")
in the__init__.py
file of the plugin.Failed to instantiate plugin example: No module named 'coreplugins.example'
and observe how nothing around tells you thatsomething went awfully wrong
. (Maybe wonder for a bit whycoreplugins
was involved, but that's a separate topic. 🙂)Additional context
I came across this when trying to figure out if a
cv2
import error was fixed in the context of this forum thread.The text was updated successfully, but these errors were encountered: