Closed superkret closed 5 months ago
Having the same problem as well. Installed from https://aur.archlinux.org/packages/neonmodem
Some on another Lemmy instance which i will refrain from naming here :eyes:
This is odd. I tried reproducing this issue on SDF and I couldn't, despite the instance seemingly using the same lemmy version as lemmy.world. It appears that the cause/one of the causes might be some configuration with these specific instances in regards to the timestamps of posts:
2024-05-17T21:05:23.490+0200⇥ ERROR⇥aggregator/aggregator.go:77⇥aggregator error: parsing time "2024-05-17T19:04:47.410256Z": extra tex t: "Z"
326
327 github.com/mrusme/neonmodem/aggregator.(*Aggregator).ListPosts
328 ⇥ /home/runner/work/neonmodem/neonmodem/aggregator/aggregator.go:77
329 github.com/mrusme/neonmodem/ui/views/posts.(*Model).refresh.func1
330 ⇥ /home/runner/work/neonmodem/neonmodem/ui/views/posts/posts.go:206
331 github.com/charmbracelet/bubbletea.(*Program).handleCommands.func1.1
332 ⇥ /home/runner/go/pkg/mod/github.com/charmbracelet/bubbletea@v0.24.2/tea.go:268
333 2024-05-17T21:05:23.490+0200⇥ ERROR⇥posts/posts.go:209⇥ [parsing time "2024-05-17T19:04:47.410256Z": extra text: "Z"]
334 github.com/mrusme/neonmodem/ui/views/posts.(*Model).refresh.func1
335 ⇥ /home/runner/work/neonmodem/neonmodem/ui/views/posts/posts.go:209
336 github.com/charmbracelet/bubbletea.(*Program).handleCommands.func1.1
337 ⇥ /home/runner/go/pkg/mod/github.com/charmbracelet/bubbletea@v0.24.2/tea.go:268
Will investigate further.
Just as a status update: I requested access to lemmy.world three days ago but I haven't received it yet. I will try with feddit.de now, just to have an account to reproduce this issue.
I tried connecting with lemmy.sdf.org since you said you couldn't reproduce the issue with SDF. Still nothing showing up, log attached.
Thanks for what you do! neonmodem.log
@superkret thank you for the log. Given that you seem to be having this issue even with SDF, I am somewhat confident that this issue has not been an issue anymore in the latest master
. I hence published a new release and would be grateful if you would give it a try and report back on whether you still experience this problem.
Just downloaded the latest release, seems to be working! I have also marked the AUR package out-of-date.
I will close this issue. In case anyone experiences any more problems with Lemmy, feel free to reopen!
Affected Version: neonmodem_1.0.4_linux_amd64 Affected System: Debian Bookworm amd64 Steps to reproduce:
neonmodem.log
I suspect this has to do with the newest lemmy version v0.19.3, since the same bug is mentioned in issue #58 from April, but none prior to that.