question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Timezone setting is not documented

See original GitHub issue

Overview

One of the examples in the Readme contains the timezone setting -e TZ=America/Los_Angeles but not reference how to use this setting.

In my case, this lead to me not using the setting, which gave me the warning /usr/lib/python3.8/site-packages/tzlocal/unix.py:158: UserWarning: Can not find any timezone configuration, defaulting to UTC. warnings.warn('Can not find any timezone configuration, defaulting to UTC.')

Steps to Reproduce

  1. On a synology NAS, mount docker image with $ sudo docker pull icloudpd/icloudpd
  2. Create folders to store photos and cookie
  3. Run docker run -it --rm --name icloud \ -v myPath:/data \ -v myPath/cookies:/cookies \ icloudpd/icloudpd:latest \ icloudpd --directory /data \ --cookie-directory /cookies \ --folder-structure {:%Y%m%d} \ --username [iCloud username] \ --password [iCloud Password] \ --size original \ --recent 3 \ --auto-delete
  4. Perform 2FA
  5. Download starts. Get the warning /usr/lib/python3.8/site-packages/tzlocal/unix.py:158: UserWarning: Can not find any timezone configuration, defaulting to UTC. warnings.warn('Can not find any timezone configuration, defaulting to UTC.')
  6. The files are successfully downloaded. It’s unclear what the effect of the timezone configuration would have been.

Expected Behavior

  • The Readme says what the setting does, and what possible values are
  • The warning says what “defaulting to UTC” means in practice

Actual Behavior

See above

Context

Steps were taken on a Synology NAS via SSH from a Mac. The files seem to copy correctly. I can’t verify if anything funky happened to the creation date and time of the photo.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:6 (1 by maintainers)

github_iconTop GitHub Comments

2reactions
boredazfcukcommented, Jan 15, 2021

I install tzdata in my Docker image and then start the container with the TZ variable to get rid of this warning.

IIRC it needs to know the time zone because it is required to calculate timestamps, presumably a dependency of the set-exif-datetime capability.

0reactions
N7l-00commented, Sep 29, 2022

F

Read more comments on GitHub >

github_iconTop Results From Across the Web

Can't set time zone automatically - Windows Client
To resolve this issue, the IT administrators should make sure the setting Set time zone automatically is enabled before deployment of a device....
Read more >
If you can't change the time or time zone on your Apple device
Open Date & Time settings and make sure that the option to set time and date automatically, as well as the option to...
Read more >
django timezone settings change does not affect model
However, I found that dates are set to UTC. Hence, in the project's settings I have changed timezone to be TIME_ZONE = 'Africa/Cairo'...
Read more >
Changing Timezone - WHMCS Documentation
If the time displayed in WHMCS is incorrect, there are two options for correcting it: Change the server clock directly.
Read more >
Set your time zone - New Relic Documentation
Some New Relic features do not rely on the User preferences time zone settings. The following use Coordinated Universal Time (UTC) and aren't...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found