|
· Föderation EN Sa 18.01.2025 17:06:20 @nick @nikclayton @Aakerbeere The underlying Mastodon issue that causes the error to be displayed in the first place is https://github.com/mastodon/mastodon/issues/25939 |
|
Föderation DE So 19.01.2025 13:07:10 @pachli@mastodon.social @nikclayton@mastodon.social Great. Thank you, Nik. My screenshot (not a 503, but complaining about malformed JSON) results from #Pachli being connected to a #Mammuthus instance (not #Mastodon). And in the bottom it shows the known date time parsing issue. Btw.: Did you manage to connect your Mammuthus test account to Pachli? (Our conversation in December '24). |
|
Föderation EN Mi 22.01.2025 23:39:37 @nick Not yet. That got swallowed up by a combination of the end of the year, and then this notification changes as part of the anti-harassment work. Can we pick that up again the week after next? The next week is going to be spent getting everything ready for the end of month release. |
|
Föderation DE Do 23.01.2025 07:04:40 |
|
Föderation DE Mo 12.05.2025 12:23:39 Hi Nik. Also the latest #Pachli 2.12.0 is still not able anymore to handle ISO 8601 dates/times like 2025-05-12T12:00:13+02:00 This works: 2025-05-12T10:00:13.000Z I did not test 2025-05-12T10:00:13+00:00 Do you still plan to check your code changes? |
|
Föderation EN Mo 12.05.2025 12:48:21 @nick Ah, I'll try and get to that later today. Technically the server is out of spec (the API should be returning a specific subset of RFC3339, see https://docs.joinmastodon.org/api/datetime-format/#datetime). The fractional second part is missing, which I suspect is what's causing the error. |
|
Föderation DE Di 13.05.2025 08:59:09 @pachli@mastodon.social Thanks. It was working in the past, so i wonder, what change in #Pachli caused this. For me the #Mastodon doc isn't 100% clear. It references RFC 3339, but doesn't really limit this to a specific subset or UTC only or something. Anyway, i did changes in my #Mammuthus code recently, so it delivers now UTC using .000Z ending. On geschnacke.de currently the latest version still with ISO 8601 / RFC 3339 / RFC 9557 date/times including the time zone is running... to allow testing... Let me check, if i can find something regarding your app / account registration issue... https://docs.joinmastodon.org/api/datetime-format/#datetime |
|
Föderation EN Di 27.05.2025 10:51:39 @nick The version of Pachli Current that's rolling out now includes the fix for this. The actual problem was that -- earlier -- geschnacke.de was returning DateTime values without the timezone, e.g. ``` (the missing sub-second part was a red herring) I just looked at the API responses from geschnacke.de again and it looks like you've also fixed this in the server. |
|
Föderation DE Mo 02.06.2025 07:20:31 Thanks for your feedback and fix... ... but... i'm a little bit confused. No code change on geschnacke.de recently... i keep it on an older version to allow you testing. And it always should put out the ISO 8601 format like this: 2004-02-12T15:19:21+00:00 I'm not sure, how you could get a value without a timezone. Do you remember the time frame, when you saw this? And btw.: It worked with #Pachli in the past until this specific version... And next btw.: As mentioned: Newer versions of #Mammuthus will deliver a UTC time with Z notation via the more or less #Mastodon compatible client API. |
|
Föderation EN Mo 02.06.2025 14:54:28 > Do you remember the time frame, when you saw this? Approximately two weeks ago. > It worked with #Pachli in the past until this specific version Yes. I'd made some changes to use a Java `Instant` instead of a Java `Date`, and parsing an `Instant` from a `String` was less lenient. https://github.com/pachli/pachli-android/pull/1544/files is the specific PR that fixed it, https://github.com/pachli/pachli-android/pull/1544/files#diff-074ef7ee7f189cd7952fdfca3faa4b8fcc0c6807f4271ad13ebf8f57e33afefdR74 is the format of date-as-string I was seeing from the server. |
|
Föderation DE Di 03.06.2025 07:17:47 Weird. Checked this, last official update on geschnacke.de was on 6th of May... after this i just did a quick patch, after i noticed an issue, around 16th of May... but this was related to the processing of personal inboxes. No change regarding the client API... and the date/time should never miss the time zone... but i can't rule out, that some configuration on the hosting provider part may have an impact on how this specific PHP function works. Did you see this date/time with missing time zone information just once or for some longer time? And btw.: I assume, you could now connect #Pachli to your account on geschnacke.de, right? And it looks like (following your provided URLs), that you now test for some more variants of a date/time value?! 1994-11-05T13:15:30.000Z That's nice... |
|
Föderation DE Mi 25.06.2025 15:28:37 Thanks again for the fix. Tested myself with #Pachli 2.13.0 on geschnacke.de. Now i have updated geschnacke.de to the currently latest version of #Mammuthus (from v885 to v907). |