Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
pleroma
pleroma
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 382
    • Issues 382
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 58
    • Merge Requests 58
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Pleroma
  • pleromapleroma
  • Issues
  • #1681

Closed
Open
Opened Apr 12, 2020 by Mew Mew@mewmew
  • Report abuse
  • New issue
Report abuse New issue

Pleroma is using the wrong timezone to create flake ID's

Probably same cause as #1671. After moving from a server using UTC time (in Nevada) to a server using CEST time (in Germany), no new posts were added to profiles, timelines, etc, because they were being given flake ID's with a lower value than the highest ones that already existed. Changing the server to use UTC time did not resolve the issue - but after waiting for a few hours, the generated ID's were high enough to make the issue non-apparent. This should probably be resolved by always using UTC to generate ID's.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: pleroma/pleroma#1681