-
Notifications
You must be signed in to change notification settings - Fork 766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
not a tuple #4196
Comments
https://diff.hex.pm/diff/tzdata/1.1.1..1.1.2 Looks like the tzdata dep needs bumped to 1.1.2 to get the updated timezone database |
Full error
|
Nice find, although my logs don't show this behavior, presumably due to different time zones. Edit: My log format is YYYY-MM-DD (for example: 2024-07-15 17:21:48.603, while yours is MM DD) tzdata 1.1.2
Next release will have tzdata 1.1.2 "automatically" |
Yep, lau/tzdata#147 Local tzdata update and then rebuild
|
Will the other ~1/2 of the dependencies get updated?
|
I wonder since a while why Dependabot not saying anything. Seems like Adrian disabled it for mix 2 years ago: |
Shame Adrian didn't say why he disabled it. But I imagine it was because he couldn't keep up with the updates. Which is a problem that I regularly face with my projects. |
Yes, I assume the same, but anyway, will start with updating tzdata and then one step at a time. |
i STILL get the same error even w/ latest 1.30.1(
Please advise) |
The WIP changes needed to bump to Phoenix HTML 4.1 are at https://gist.github.com/sdwalker/a057d9f8f3425efb746f6805ce087beb |
It is not fixed in TeslaMate 1.30.1, so this is expected behavior till a new version is released. |
ok, is there ETA for new version? or is there another known version that works? i tried to rollback few version behind, however still couldn't get it to work due to same error, also why is this issue closed if this still isn't resolved.. |
This issue described by OP is cosmetic nature. As the dependency always had the issue a rollback does not result in different behavior. |
it's not cosmetic nature, as i can't start Teslamate inside of the docker container because of that issue though.. whenever i try to access my url, I get
and when I look into the logs of Teslamate, I See this error
|
The issue described by OP is cosmetic nature. If your instance is not starting, please check your tz config in your |
-> #4277 |
Is there an existing issue for this?
What happened?
Seeing a
not a tuple
error periodically in my logs. Seems to be associated with TzData. Was happening once an hour, and last occurrance was 2024-09-13 03:20:06UTC.Possibly a bug from tzdata, maybe there was some sort of error condition with its update.
Expected Behavior
Error should not appear.
Steps To Reproduce
Run teslamate for a while and look at the logs.
Relevant log output
Sep 11 11:19:55 iot2 teslamate[24319]: * 2nd argument: not a tuple Sep 11 11:19:55 iot2 teslamate[24319]: :erlang.element(1, :error) Sep 11 11:19:55 iot2 teslamate[24319]: (tzdata 1.1.1) lib/tzdata/util.ex:223: Tzdata.Util.to_int/1 Sep 11 11:19:55 iot2 teslamate[24319]: (tzdata 1.1.1) lib/tzdata/parser.ex:38: Tzdata.Parser.process_rule/1 Sep 11 11:19:55 iot2 teslamate[24319]: (tzdata 1.1.1) lib/tzdata/parser.ex:24: Tzdata.Parser.process_tz_list/1 Sep 11 11:19:55 iot2 teslamate[24319]: (tzdata 1.1.1) lib/tzdata/parser.ex:86: Tzdata.Parser.process_zone/5 Sep 11 11:19:55 iot2 teslamate[24319]: (tzdata 1.1.1) lib/tzdata/parser.ex:24: Tzdata.Parser.process_tz_list/1 Sep 11 11:19:55 iot2 teslamate[24319]: (tzdata 1.1.1) lib/tzdata/parser.ex:86: Tzdata.Parser.process_zone/5 Sep 11 11:19:55 iot2 teslamate[24319]: (tzdata 1.1.1) lib/tzdata/parser.ex:24: Tzdata.Parser.process_tz_list/1
Screenshots
No response
Additional data
No response
Type of installation
Manual
Version
57acace
The text was updated successfully, but these errors were encountered: