Merged
Conversation
Ark-kun
approved these changes
Feb 21, 2026
Collaborator
Author
camielvs
force-pushed
the
02-20-fix_rm_manual_timezone_adjustments
branch
from
f825766 to
437b3f3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The backend was recently updated to return timezone alongside date strings, so the manual timezone adjustment is no longer needed.
Since the backend was updated this manual adjustment has been causing erroneous times to be reported on runs and pipelines. The issue is currently on Production.
Related Issue and Pull requests
Type of Change
Checklist
Screenshots (if applicable)
Create a run & confirm that in the run list it shows the expected time. Same for pipelines.
Test Instructions
Additional Comments