Problem/Motivation

The ScannerService from l10n_drupal_reset imports projects and releases from a releases.tsv file from drupal.org.
That file contains a date string for each release, which is in UTC.
However, ScannerService will import releases in the system timezone.

Steps to reproduce

Set a different system timezone, run connector scan
Expected: Same timestamps on imported releases.
Actual: Timestamps on releases will be different.

Proposed resolution

See MR.

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork l10n_server-3592848

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

donquixote created an issue. See original summary.

donquixote opened merge request !124

donquixote’s picture

donquixote commented
Status: Active » Needs review

fmb made their first commit to this issue’s fork.

  • fmb committed 09e15c47 on 3.0.x 
    Merge branch '3592848-scannerservice-timezone' into '3.0.x'

Resolve #...

  • fmb committed 9a404020 on 3.0.x authored by donquixote 
    Issue #3592848: Fix: Always use UTC for dates in parseProjectList().

  • fmb committed 43320a7a on 3.0.x authored by donquixote 
    Issue #3592848: Test ->scanHandler() with different timezones.
fmb’s picture

fmb commented
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.