influxdata / influxdata/influxdb

Tasks are not started according to local/given timezone

Open
#23,257 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

Steps to reproduce:

  1. Schedule a task for every day
  2. Define timezone options inside the task:
    option location = timezone.location(name: "Europe/Berlin")

Expected behavior:
I expect the task started at midnight of the given timezone (in my case local timezone).

Actual behavior:
The task start at midnight UTC, which is currently (CEST) two hours off.
Every range or other timezone-related query data are correct, so it's only the starting time.

Environment info:
Docker image with correctly set timezone

Contributor guide

Open the contributing guide

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.

Research direction

Reproduce the daily task with option location = timezone.location(name: "Europe/Berlin") in the provided Docker environment, then trace how its scheduled start time is calculated. Compare the task start with the timezone used by the range and other timezone-related query data. Done means the task starts at midnight in its configured timezone rather than midnight UTC.

Written by the indexing model from the issue text.

Assessment

Domain
databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.