Several bugs identified, Oct 13/2023
Hi folks,
Digging into issues with messages today, a few bugs were identified and will be being addressed ASAP. For information you can check the issues opened at the Helpdesk here:
https://gitlab.com/routhio/theden/helpdesk/-/boards
The messages issue and the accounts being reaped issues should be fixable this weekend. The issue with some verification tokens causing the client backend to crash will take longer as the frontend is in the middle of a major refactor. If you get a 502 error when trying to verify your account, please try logging in once the site loads again, your account will already have been verified.
For any users having issues accessing the site, please open a ticket a the Helpdesk : https://gitlab.com/routhio/theden/helpdesk/-/boards
Replies
Routh
I want to apologise for the delay here; I ripped down the staging site and it’s infra space on the production cluster as part of a cost savings effort just before the discovery of the source of these issues.
I am just about through the re-arch of my at home on-prem servers to support running all this from home again. Just need to ensure I have it setup to be prod-like so I can reproduce and verify the problem and verify it’s solved on staging. I’ll have these addressed as soon as I can.
Routh
Finally through the slog of getting the infra re-architecture done and now able to move on to these fixes.
Routh
The following bugs are now fixed:
Users getting 403 errors on messages endpoints, causing them to be unable to view messages.
Unverified users being removed before 14 day time limit.
Users getting 403 errors on mark all and clear all options.
Apologies for the delays in resolving these.
Routh
I’ve noted that since the updates that came with these fixes, mobile sessions in Firefox and Edge on Android are not able to stay alive for the full 24 hours, but I’ve not yet understood why. Desktop versions of the same browsers seem unaffected.. I’m looking into it.
FWIW, if you encounter a weird state because of this on mobile, just refresh the page and log back in.
Routh
Session persistence is fixed, along with all issues except whatever is causing about 1 in 20 verification tokens to crash the app after verification completes. That last one is a bit hard to track down as the actual error gets cut off the logs.