Make DateTime objects use naieve timezone
Bug #1322033 reported by
Thomi Richards
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Autopilot |
Fix Released
|
Critical
|
Unassigned | ||
| autopilot (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
If an app is storing a local date time, autopilot-qt will export it as seconds since the epoch, UTC time. Qml apps don't seem to be able to set the timezone, so Qt assumes the date is in UTC. On the python side however, we ask python for a date time object and assume that the timestamp is UTC. This means that the times we get client-side are all incorrect.
To fix this, we need to not assume that the timestamp is in UTC, and instead just ignore the timezone factor. This may cause us problems down the road, but it seems like a quick fix for now.
Related branches
lp:~thomir-deactivatedaccount/autopilot/temp-dev-fix-timezones
- PS Jenkins bot: Approve (continuous-integration)
- Christopher Lee (community): Approve
-
Diff: 193 lines (+68/-47)4 files modifiedautopilot/introspection/types.py (+1/-1)
autopilot/tests/functional/__init__.py (+33/-1)
autopilot/tests/functional/test_input_stack.py (+5/-45)
autopilot/tests/functional/test_types.py (+29/-0)
Revision history for this message
| PS Jenkins bot (ps-jenkins) wrote | #1 |
| Changed in autopilot: | |
| status: | Confirmed → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in autopilot (Ubuntu): | |
| status: | New → Fix Released |
| Changed in autopilot: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix committed into lp:~autopilot/autopilot/temp-dev at revision 512, scheduled for release in autopilot, milestone Unknown