fix(study-rooms): specify and serve UCI timezone for slots #85
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Followup to #75, fixing study room slot times being rendered in Postgres's local timezone.
We simply set the timezone on the connection acquired by the scraper to
America/Los_Angeles
.Related Issue
Resolves #84. We both specify the intended behavior from #75 in the example and actually fulfill it.
Motivation and Context
How Has This Been Tested?
Tested by setting Postgres's timezone to
America/New_York
, running the scraper, then testing the API request.Screenshots (if appropriate):
Despite forcing Postgres's global timezone to change, the timezone is correct since we set it on the session which takes precedence over the global setting:
We know this is effective because setting a different timezone for the scraper's SQL session uses that timezone instead:
So if we force
America/Los_Angeles
on the scraper session, it will give the correct offset regardless of Postgres or system timezone.Types of changes
Checklist: