search

speezepearson / biatob

1 stars 0 forks source link

I landed on a weirdly blank page after clicking "I trust this person" #11

Closed orborde closed 3 years ago

orborde commented 3 years ago
  1. Clicked on https://www.biatob.com/invitation/dreev/FmDZp0Wk_pHeofLdf1PTaQ
  2. Logged in using the login form at the top of the page.
  3. Clicked "I trust this user" or whatever the button is.
  4. Landed on a page that looks like the attached.
  5. Seems like a weird landing point!

image

orborde commented 3 years ago

Refreshing the page landed me at exactly the same view. Hard-refreshing (or whatever Control+Shift+R does in Chrome) took me to the normal biatob.com homepage, though.

speezepearson commented 3 years ago

Hrrm, I'd hoped that that problem was just a "me" problem. I pretty reliably hit this bug when I log in on /welcome, in Firefox, but not in Chrome.

Here's me tailing the logs, typing my own comments into the terminal:

I am about to log in on /welcome
{"actor": null, "event": "username logged in", "servicer_action": "LogInUsername", "timestamp": 1622700210.8791735, "username": "spencer"}
{"action": "get_welcome", "event": "web request succeeded", "path": "/welcome", "resp": "<Response OK not prepared>", "status": 200, "timestamp": 1622700211.045718}
{"action": "get_elm_module", "event": "web request succeeded", "path": "/elm/Welcome.js", "resp": "<FileResponse OK not prepared>", "status": 200, "timestamp": 1622700211.2861006}
^ that last line appeared after almost exactly 30 seconds.
But Firefox says its request for `https://biatob.com/elm/Welcome.js` 404ed after only 48ms.

I am about to refresh the blank /welcome page
{"action": "get_welcome", "event": "web request succeeded", "path": "/welcome", "resp": "<Response OK not prepared>", "status": 200, "timestamp": 1622700345.416498}
{"action": "get_elm_module", "event": "web request succeeded", "path": "/elm/Welcome.js", "resp": "<FileResponse OK not prepared>", "status": 200, "timestamp": 1622700345.5898209}
^ Again, that last line took ~30sec to appear. But the first line did too. I think there's some delay in NFS's logging system.

So... I think the delay is a red herring. My logging says it's returning a 200 response, but Firefox think it's a 404. Yuck.

speezepearson commented 3 years ago

Things that I can still reproduce the error after doing:

This doesn't happen locally, only on biatob.com. Hrrm.

speezepearson commented 3 years ago

I've stopped being able to reproduce the problem, after applying 629058c. Please let me know if the problem persists/recurs!