fix(forecast): capture live observation time with telemetry - #1127
Merged
Conversation
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_cc4ece45-a7c8-4475-99d7-57fd7da4aa39) |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
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.
A delayed forecast archive write can leave the observer's ticker time behind the latest power readings. The observer then treats fresh readings as future data and clears the current learning interval.
Use the existing telemetry snapshot method that captures the time after acquiring the read lock. Use that same time for observation intervals, availability and curtailment checks. The ticker now only wakes the observer. Explicit forecast origins, frozen issue inputs and the bounded archive retry and shutdown paths keep their current behavior.
This addresses the late review finding on #1125 before publishing the next beta.
Validation:
make verifypasses.Note
Medium Risk
Changes live forecast observation timing and interval completion logic, which feeds learning and archived observations; risk is mitigated by focused regression tests and unchanged explicit-origin paths.
Overview
Fixes lost 15-minute forecast learning intervals when archive writes delay the observer tick. If
observeran with the ticker’s schedulednowwhile newer meter/PV samples were already in the store, interval logic could treat those readings as future data and drop the in-progress quarter.Live observation now only uses the ticker as a wake-up:
observecallsForecastMeasurementNowand derivesnowfromr.Atafter the telemetry read lock, so measurement time, curtailment checks, andobservationIntervalsstay aligned with the snapshot. Explicit forecast origins and frozen issue capture are unchanged.Adds regression tests for the delayed-observe scenario (full quarter retained at 1200 W load / 800 W PV) and confirms a 3+ minute gap still rejects the quarter. Call sites and occupancy tests updated for the parameterless
observe(ctx).Reviewed by Cursor Bugbot for commit e3076a4. Bugbot is set up for automated code reviews on this repo. Configure here.