Skip to content

[Worker] Missing timezone in pgq causes incorrect Job run_at refresh #91

Description

@rohilsurana

When running postgres and entropy server on different timezones, the pgq can pickup jobs that are not supposed to be picked yet and update their run_at to the postgres server time + extended interval seconds.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions