Closed instancer-kirik closed 1 month ago
Yep, just saw the same after updating.
[error] GenServer :tzdata_release_updater terminating
** (ArgumentError) errors were found at the given arguments:
* 2nd argument: not a tuple
:erlang.element(1, :error)
(tzdata 1.1.1) lib/tzdata/util.ex:223: Tzdata.Util.to_int/1
It seems this have been an issue which is marked as resolved, but isn't. From what I understood by a quick glance, the source data might have changed and causes issues. #143
@namxam Is this after upgrading to tzdata v1.1.2 ?
Honestly I don't know, because the error is handled gracefully. I just noticed it in a project I am not working on often. I know I updated a few dependencies but I am not sure if tzdata was among it. I will check when I am back at my computer.
Was greeted with the same error this morning, Upgrading from tzdata 1.1.1 => 1.1.2 fixed this for me.
Was greeted with the same error this morning, Upgrading from tzdata 1.1.1 => 1.1.2 fixed this for me.
Thanks it saved me some time.
I think the tzdata dep in our project is actually coming from here: https://github.com/bitwalker/timex/blob/c45b9a734074ac2a56355ec52ebf931b932223b7/mix.exs#L58. Our lock file says 1.1.1 so I'll update and see if that resolves it.
This should be fixed in the v1.1.2 release: https://github.com/lau/tzdata/commit/e63fc28c02d79dec9ea56e6cecf721f595a18495
Woot!
~anyone else still seeing this error even after updating to 1.1.2?~
You shouldn't be seeing this error as of 1.1.2. Check and make sure your mix.lock is showing :tzdata, "1.1.2"
in case you had some sort of dep shenanigans @hebbo.
You shouldn't be seeing this error as of 1.1.2. Check and make sure your mix.lock is showing
:tzdata, "1.1.2"
in case you had some sort of dep shenanigans @hebbo.
Thanks @treshenry you are right. After writing the post we realised we actually never deployed the update in Production. False alarm.
I did start off with my config as
config :tzdata, :data_dir, "priv/tzdata"
which also had this error on mix phx.server and is now