Fix Time Machine#1203
Merged
stevekuznetsov merged 1 commit intoJul 2, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This adds a hard coded timestamp to the date that's set from Time Machine to keep API calls consistent.
We noticed an issue where depending on the time of day you change Time Machine, some APIs are returning different day results. The most noticeable example was the difference between the
map-layerandproducts?avalanche_center=&date_start=&date_end=calls we're making. The reason is thatfetchAvalancheForecastinuseAvalancheForecastcallsnominalForecastDatewhen fetching an avalanche forecast fragment. This calculates the date based off the avalanche center'sexpiry_timeand changes the date based on if we know that the the avalanche center has a new forecast available.The fix here forces the calls to be made within the same day so that there's no mismatch by adding a timestamp to the date instead of using the on device timestamp. This is only used for testing in Time Machine so it should give us the results we want even if under the hood we're potentially showing "wrong" data.