Requests for all:* page 2 timeout.

Submitted ⁨⁨1⁩ ⁨month⁩ ago⁩ by ⁨GeekMan@sh.itjust.works⁩ to ⁨main@sh.itjust.works⁩

Multiple Lemmy apps serve the first ‘page’ of posts fine - even new posts or updates - but upon scrolling and requesting the next page, Boost gives an error message “timeout”, and Blorp just doesn’t load anything else (per app implementation, I know).

source

Comments

Sort:hotnew top

TheDude@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
Hey all, I’m travelling at the moment but have been in discussions with the other admins about this issue. I return Friday oct 31st and will schedule to get us upgraded to 0.19.13 shortly after. I won’t be giving the typical 5 day official notice to not create any extra delays. The upgrade to 0.19.13 is minor and shouldn’t take us too long to run. Thank you for being patient.

source
- AChiTenshi@sh.itjust.works ⁨4⁩ ⁨weeks⁩ ago
  Unfortunately the issue is still persisting.
  
  source
- pelespirit@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago
  I think you’ve been back for a little while. Is this out of your control? I see you upgraded, but the next buttons still don’t work. Any updates would be greatly appreciated.
  
  source
- Flames5123@sh.itjust.works ⁨4⁩ ⁨weeks⁩ ago
  Yea, not sure if the update has been run yet. We’re still getting the issue of not being able to load page 2. Any ETA on this?
  
  source
  - westingham@sh.itjust.works ⁨4⁩ ⁨weeks⁩ ago
    I haven’t seen anything here: sh.itjust.works/c/announcements
    
    I’m guessing it’s not done yet
    
    source
- GeekMan@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
  No worries! Thanks for the fix, and running the instance.
  
  source
- StarvingMartist@sh.itjust.works ⁨4⁩ ⁨weeks⁩ ago
  Thank you for your hard work, it’s great to hear I won’t be leaving this fine instance after all
  
  source
SeventySeven@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
I am so glad someone mentioned this! The past 2 or 3 days this has been happening to me and I thought it was just on my end, I thought I was going crazy! Only happens on my mobile app. I am using the Jerboa app for reference. Using a web browser is fine though. Perhaps an API issue? I am not sure. I recommend just using it on a mobile web browser for the time being.

source
- drrodneymckay_@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
  I also wanted to add my feedback, but life is always busy. I’ve been experiencing the timeout in boost on android for a few days across multiple internet connections, so I was pretty confident it’s not a ad block, vpn, content filter. Unfortunately it hasn’t made it to priority for me to track in any of my systems. I might be able to log and capture traffic is needed. I’m a network engineer with access to some enterprise grade network gear, unfortunately my primary desktop computer just died due to bad windows update, RIP last install. serving me well for many many years.
  
  source
AChiTenshi@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
Just going to add myself to the group of people experiencing this issue.

This issue appears unrelated to the client as I see it in bothering jerboa and in web browser.

source
- AChiTenshi@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
  I just discovered that a sorting by Top Day does not show this issue. New, Hot, Actove, Most Comments all have an issue where they time out after showing the first set of results.
  
  source
moseschrute@lemmy.world ⁨1⁩ ⁨month⁩ ago
Blorp dev here. I would love to get this resolved. Could you be more specific?

If you’re on the web: could you link the specific page(s) you are seeing this error on?

If you’re on the app: which screens are you on (e.g. all feed, local feed, subscribed feed, a specific community feed)

It’s easier to debug things on web, and Blorp shares 99% of the code between app and web. So if possible, could you recreate the issue on web, and link that? Knowing what instance you’re using (I assume sh.itjust.works), is also helpful.
source
- GeekMan@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
  I’m so sorry for my delay. Just had a hell of a weekend at work and only just resurfaced.
  
  To give you some more detail (it might not be good enough for QA but I’ll try)…
  
  Blorp 1.9.4, Pixel 7, Android 16.
  
  I mentioned in the title of the OP that the issue occurs when browsing All/* (New/Hot/Active).
  
  For Blorp, the issue presents after I load All/anything, then scroll through the feed until it stops, I assume it should have infinite scroll, I keep gesturing ‘up’ (to scroll down more), but no more posts appear.
  
  I can scroll back up to the top and gesture ‘down’ to make it refresh and it does, but just the initial 50 posts then no more
  
  I assume 50 posts is the first-page fetch.
  
  My initial post was also triggered by my experience in Boost, which actually shows a ‘timeout’ error popup, about 30-60s after scrolling to the end of the first page-feed.
  
  Lemme know if you need more details.
  
  source
duckythescientist@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago
This still seems to be broken on 0.19.13 (sh.itjust.works/post/49612706)

source
- AChiTenshi@sh.itjust.works ⁨2⁩ ⁨weeks⁩ ago
  Not sure what changed but it seems to be working as of today.
  
  source
Ghyste@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
@TheDude@sh.itjust.works have you seen this yet?

source
Corkyskog@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
Seconded, using Jerboa

source
threelonmusketeers@sh.itjust.works ⁨1⁩ ⁨month⁩ ago
Huh, and this is specific to sh.itjust.works?

source
- GeekMan@sh.itjust.works ⁨1⁩ ⁨month⁩ ago
  I’m not sure if that, sorry. That’s just my primary (?) instance, and I’ve seen it happen before and saw another post thinking it was the instance, too.
  
  It might not be just the instance, since it only happens when aggregating ‘all’, and not local or subbed.
  
  Bear with me. I’m a relative newbie to Lemmy & federation.
  
  source
  - Flames5123@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
    I can confirm it’s just sh.itjust.works. I logged into my lemmy.world account in voyager and can just scroll and scroll.
    
    source
Flames5123@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
Chiming in here. It’s affecting me on mobile and website. What is going on? What’s the solution? 3 days for this is too crazy imo.

source
westingham@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
I’m having this issue as well, using both web and Voyager

source
Switorik@lemmy.zip ⁨4⁩ ⁨weeks⁩ ago
I’ve been experiencing this issue since the first pie feed update ~2 months ago using boost and jerboa. The issue doesn’t affect me on sync, thunder, or guest mode on boost. I’m suspecting it is the sorting algorithm (new, hot, etc).

source
AChiTenshi@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
It’s an older issue (from earlier this year) but I wonder I’d this bug is related. github.com/LemmyNet/lemmy/issues/5376

Anyone know what version sh.itjust.works is running?

source
- threelonmusketeers@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
  According to the footer of the web interface, sh.itjust.works is running Lemmy 0.19.12 at the moment.
  
  source