this post was submitted on 28 Jul 2023
173 points (100.0% liked)
/kbin meta
110 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ok, so in the next few days, I'll be testing some things. It might be a bit worse for a while, but it will definitely speed up the problem-solving process. I'll be grateful for any feedback. I'm unable to reproduce it in local/testing environments, so it might be an issue with the cluster.
Is there anything we can help with? provide logs, repeat steps, etc?
I'm not sure if it helps, but I wonder if this is linked to the inactivity error.
Load up any kbin thread or main page, open a new browser tab in the foreground, me around in the non-kbin tab for 15-30 minutes, and return to the kbin tab. Now any clicks on 'actions' (voting, posting, basically sending info to the server) sends you to an error page. Whatever info you were sending doesn't register (vote count or highlight, posts don't show up, etc.
I didn't have any logout problems at all until maybe a week ago. Since then I've been logged out 5+ times.
Not a big problem for me, but I could see it annoying others.
I've seen the same. Leaving an app or browser tab open for a while, then interacting, seems to cause it.
Slightly annoyingly spending 10min drafting a comment seems to cause the same on occasion. (I guess there is no activity outside the edit box).
Fortunately if I get an error after posting, usually going back means the text is still there, then it's usually copy the text, click through to the profile of the person I was replying to and post the comment from that page. So far that almost always works.
Weirdly I don't seem to get logged out, just randomly directed to a error page when interacting (e.g. upvoting or trying to comment).
Edit: I don't think I can reliably recreate this issue...
I've developed a habit of copying everything I write before I hit send, because my comments tend to take a long time for me to write/format to my liking. Not because I keep losing it, but just in case.
Usually when it times out in the comments, I get brought to a page containing my lone comment box and a notification about "something-something, this page is federated, click here to return to the comments section."
So I wonder if it's really related in part to the page's continually updating federation making whatever you're trying to interact with obsolete. Though that doesn't make as much sense to me on our timelines as it does in a comment section :/
I've only had to dig around in someone else's profile twice, and that was because the notification's link to whatever reply you're trying to check doesn't seem to be mixing with numbered forum pages. By the time I check my replies, they're usually on a different page than I'm being linked to.
I don't think this has to do away with the numbering, it would just require a different method of linking (right?). But it IS one of the finer annoyances, and that I usually consent to scan/reread the entire thread looking for my avvie speaks to how stubborn I am.
Same. I’ve only ever seen this error after some time of inactivity, and reloading the page always helps.
I've had a similar experience. Only thing I can add is that more rarely even refreshing the page doesn't resolve running into an error page when voting on some comments. However, each time I was able to visit the user's profile and vote from there without issue.
This is anecdotal, but I don't experience these log outs on fedia (I have to relog like once every few days but that doesn't bother me, I assumed it was cookie expiry but maybe it has to do with server restarts or something). So I can understand if it happens more often to kbin social users it might be some other way it's set up like caching or something that others might not be running. Then again, without version info, it makes it a bit tough to debug so this might not be helpful, fedia could be running some random sha atm which might be the reason.
Apparently, the error condition might NOT be dependent on idle time (a period of time without any interaction). — Evidence: Periodic clicks on a vote button, scripted at 45-second intervals, did not prevent the error's eventual occurrence.
I really appreciate how proactive you are. Thank you for your hard work.
Pretty sure that for me it only happens if I'm reading a page without interacting for a while.
Then any interaction, like upvote, is error, but refreshing the original page fixes it.
(Firefox on android)
If I had to guess it’s probably the stickiness of the session (which user is assigned to which server on the cluster) that expires after a certain time which leads to needing a new login or in the case of the error page a CSRF token which isn’t valid on this server of the cluster.