Open smeagolthellama opened 1 year ago
Weird. So the server is sending a "created_at" time stamp of 0. That is weird, but probably shouldn't cause toot to crash. I'll look at it if I can get a server login there.
By the way, it seems to have resolved itself after a day or two. My guess is that it sent a nulled post as the terminator for the list of posts it sends (although I don't know why it would have sent less than a page or two worth of posts, as I've had this account for a couple months at this point). Also, the server has had an update since then, so that also might have solved the issue.
Thanks for the update. So if I test now, it won't exhibit the behavior. OTOH, toot should not crash in response to invalid input of this kind. So I can simulate the problem by setting the "created at" timestamp to 0 / null and see what happens.
I just logged in for the first time via toot (to the server at fe.disroot.org, which is running
Mastodon 2.7.2 (compatible; Akkoma 3.8.0-0-gb86b3a9-develop)
according totoot instance
, in case it's a server-specific thing), and bothtoot tui
andtoot timeline
fail with an error similar to the one seen at #114, except referring to what appears to be the unix epoch.Actually, now
toot timeline
only shows the error when I say yes to the first "Continue?" dialogue. I've attached the error fromtimeline
.toot version: 0.34.1-1 from the devuan repos python version: 3.11.2 operating system: devuan (daedalus) linux (think debian w/o systemd)