-
Notifications
You must be signed in to change notification settings - Fork 73
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
Upgrading from 0.6.5 to 0.6.6 ends with (CryptoClient) uncaught exception #321
Comments
I'm not able to reproduce this, unfortunately. Adding the following to the top of your bot's main file might reveal the actual contents of LogService.muteModule("Metrics");
LogService.trace = LogService.debug;
LogService.setLevel(LogLevel.TRACE); |
Hi, really, there isn't anything new when I apply for those 3 lines. Here there are the complete logs with them enabled, apart from some "own" initialisation stuff that I add at the beginning (and omited in the original report) the error happens almost immediately.
Ciao :-) |
I'm also getting this error, clearing persistent storage and logging in again solves it but I'm hoping not to have to force everyone to do that. What do you need to help reproduce? |
For the records a few days ago I proceeded to update out staging bot to v0.7.1 and completely remove the storage (to get a new token and so on). It has been running @ staging without problem (just a lot of "Can't find the room key to decrypt the event" at the beginning, until it got everything updated). So, today, I've been brave enough to apply for the same (update and delete storage) with the prod bot, and it's up and, apparently, running ok. I'll keep monitoring it, but for sure the problem reported in this issue (immediately after starting) is not happening anymore. Ciao :-) |
Update: We have 0.7.1 running (after deleting storage) here since a few days ago in prod, and it seems that this problem isn't happening anymore. We are facing #346 a few times (old-known issue for us), but other than that, all ok. Ciao :-) |
Describe the bug
Trying to upgrade from sdk 0.6.5. to 0.6.6 consistently get the follow error on startup):
To Reproduce
Steps to reproduce the behavior:
npm update matrix-bot-sdk
npm i
ornpm ci
LogLevel.DEBUG
).Expected behavior
The bot starts working normally, like it was with 0.6.5.
Log snippet
Additional context
The
M_NOT_FOUND
errors are pre-existing, happening always, as many times as encrypted rooms the bot is in (seems like). I imagine that those errors are unrelated with the new one, reported here, causing the bot to stop on startup.Ciao :-)
The text was updated successfully, but these errors were encountered: