FeedLand intermittently fails to respond?

Open
#270 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
backend

Research direction

Start with the linked post and the reported appServer layer, then compare the news page behavior with the higher-level FeedLand symptoms described here. The issue names no files, tests, or concrete fix; done would require isolating the intermittent no-response cause and defining a corresponding change.

Written by the indexing model from the issue text.

Description

A place to comment on this post.

A couple of weeks ago I found and fixed an error in "PagePark" that made "FeedLand" and "Drummer" fail. The apps were offline until I could restart the server, and that sometimes meant hours of downtime. That no longer happens. But now there's a different problem, sometimes I go to my news page on feedland.org and for a minute or so there's no response. Eventually I give up and try again in a new tab. Same thing. Eventually the problem clears and the server returns to it's normal performance. I'm starting to think about how I might isolate this problem. My theory is that the problem is in the appserver layer, not in FeedLand itself, because when it happens nothing is returned. If it were at a higher level, the lockup would be in the code that gets a timeline or feedlist or whatever, so you would see a menu at the top of the screen. But it's always the news page this happens on, come to think of it. Maybe I should start a thread on this in case other FeedLand users who are also developers (please) might have some ideas.

Dominant language
HTML
Stars
134
Forks
10
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.