Release v1.39.9 - #1093
Merged
Merged
Release v1.39.9#1093
Conversation
The form's start defaults to the minute it opened, so a workout logged right after it finished was stored as ending up to a day ahead. The duration now fails validation when start + duration lies past now, with the same one-minute slack the start check uses.
… and the AI response time everywhere
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
1 participant
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.
Log a workout by hand (#1085), a page for body fat (#1084), the AI response-timeout setting on every model call (#1090), the wide lab scan review (#1059), and a fix from the release review: a manual workout can no longer end in the future.
No migrations, no new settings. API:
DELETE /api/workouts/{id}(manual workouts only),ai.provider.responseTimeoutMson/api/auth/me, insights layout idbody-fat.