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 647
    • Issues 647
    • 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
  • Merge requests
  • !2395

Fix for use of `published` field from different entities

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Alexander Strizhakov requested to merge fix/1691-feed-render into develop Apr 16, 2020
  • Overview 0
  • Commits 1
  • Pipelines 1
  • Changes 6

In rare cases, activity was created at the end of a second, and an object at the beginning of the next second, so after formatting in RFC822, the activity and the object belonged to different seconds. Also in feed render was used object.data["published"], which was compared with activity.data["published"]. I've fixed feed tests.

Is it correct that the moment of creation of an activity and an object can differ in second after formatting?

Closes #1691 (closed)

Edited Apr 16, 2020 by Alexander Strizhakov
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: fix/1691-feed-render