Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 646
    • Issues 646
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 88
    • Merge requests 88
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleromapleroma
  • Issues
  • #712
Closed
Open
Issue created Mar 05, 2019 by HJ@hj🔥Maintainer

Don't die just because some posts failed to render

For god knows which time already pleroma starts timing out while FE tries to fetch timeline. This leaves FE completely broken and unusable until admin fixes the problem and restarts the whole thing.

Some suggestions:

  1. Have an internal timeout for rendering a request and each post.
  2. When request timeout is upon us, just render what's ready, drop every unrendered post (put them into queue to re-render in safe mode* maybe?)
    alternatively: track if request timed out and re-render entire request in safe mode next time?
  3. Log the long-running post renders/request as errors so it's easier to debug them.

*by safe mode i mean render post ignoring stuff that might fail like rich media previews.

Assignee
Assign to
Time tracking