cameroncros / OctoPrint-DiscordRemote

Discord plugin for OctoPrint
MIT License
66 stars 34 forks source link

Updating to 3.11.0 causes discordremote to no longer show up as installed and unable to be configured. #233

Closed bharvey88 closed 1 year ago

bharvey88 commented 1 year ago

Describe the bug Once I updated discordremote to 3.11.0 and restarted I noticed my discord bot was offline. I restarted the pi and it still wasnt back so I went into the octoprint ui and discordremote didnt show as installed. So I then reinstalled, then restarted, and still the plugin doesnt show installed. https://imgur.com/6Zs17Ug here is a picture showing octoprint shows "unknown" was installed successfully in top right.

Logs Please find the logs and upload them here. It'll likely be the first thing that is asked for, so save some time and upload them. Logs can be found under Settings -> Logging -> plugin_discordremote.log

the only logs found in above location for the plugin are from before the update. possibly due to octoprint not properly seeing the plugin installed correctly.

octoprint.log shows this:

2023-01-08 08:17:27,420 - octoprint.plugin.core - ERROR - Error loading plugin discordremote Traceback (most recent call last): File "/home/pi/oprint/lib/python3.7/site-packages/octoprint/plugin/core.py", line 1274, in _import_plugin module = _load_module(module_name, spec) File "/home/pi/oprint/lib/python3.7/site-packages/octoprint/plugin/core.py", line 52, in _load_module return imp.load_module(name, f, filename, details) File "/home/pi/oprint/lib/python3.7/site-packages/octoprint/vendor/imp.py", line 238, in load_module return load_package(name, filename) File "/home/pi/oprint/lib/python3.7/site-packages/octoprint/vendor/imp.py", line 212, in load_package return _load(spec) File "", line 696, in _load File "", line 677, in _load_unlocked File "", line 728, in exec_module File "", line 219, in _call_with_frames_removed File "/home/pi/oprint/lib/python3.7/site-packages/octoprint_discordremote/init.py", line 26, in from octoprint_discordremote.command import Command File "/home/pi/oprint/lib/python3.7/site-packages/octoprint_discordremote/command.py", line 16, in from discord.embeds import Embed File "/home/pi/oprint/lib/python3.7/site-packages/discord/init.py", line 25, in from .client import Client File "/home/pi/oprint/lib/python3.7/site-packages/discord/client.py", line 35, in from .user import User, Profile File "/home/pi/oprint/lib/python3.7/site-packages/discord/user.py", line 29, in import discord.abc File "/home/pi/oprint/lib/python3.7/site-packages/discord/abc.py", line 32, in from .iterators import HistoryIterator File "/home/pi/oprint/lib/python3.7/site-packages/discord/iterators.py", line 33, in from .audit_logs import AuditLogEntry File "/home/pi/oprint/lib/python3.7/site-packages/discord/audit_logs.py", line 27, in from . import utils, enums File "", line 983, in _find_and_load File "", line 967, in _find_and_load_unlocked File "", line 677, in _load_unlocked File "", line 724, in exec_module File "", line 857, in get_code File "", line 525, in _compile_bytecode ValueError: bad marshal data (invalid reference)

To Reproduce Steps to reproduce the behavior:

  1. update discord remote
  2. restart octoprint
  3. discord remote is now not showing up as installed and unable to be configured.

Expected behavior Update succeeds and plugin still works.

Screenshots https://imgur.com/6Zs17Ug here is a picture showing octoprint shows "unknown" was installed successfully in top right.

Desktop (please complete the following information):

Additional context none needed

bharvey88 commented 1 year ago

follow up - I spoke to jneilliii (octoprint / plugin dev) and he suggested trying this command via cli "/home/pi/oprint/bin/pip install --force-reinstall --no-cache-dir https://github.com/cameroncros/OctoPrint-DiscordRemote/archive/refs/tags/v3.11.0.zip" and after rebooting the plugin is now showing back up and working.

bharvey88 commented 1 year ago

second follow up - succeeded upgrading second printer plugin with no issues. Possibly a corruption issue on sd card. I wont close this just in case you think it might be worth looking into, but if you agree it's most likely just a corruption issue then please feel free to close it.

cameroncros commented 1 year ago

Im happy to close the issue, If I cannot replicate it then I cant really debug it, and it seems like you solved it for yourself anyway.