Repository navigation
docs(debug-journal): fold the 2026-10-28..11-01 queue slice (12 of 15 candidates); update entries fixed on main - #5918
Merged
Conversation
… candidates); update entries fixed on main Co-Authored-By: Claude Code <noreply@anthropic.com>
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.
🤖 Automated journal-update run, 2026-11-02 (queue slice: 15 candidates, 5556 → 5816; 73 remain queued — see note at the end)
Summary — 14 of 15 candidates folded or updated entries; 1 dropped; 2 existing entries corrected for merges that landed since. The commit subject's "12 of 15" overcounts the drops; the split is 14 folded / 1 dropped as listed below. Base was current main (
039e7c5a) before branching; every candidate was re-verified against it before folding.Folded
Solis (solis.py)row: on a parallel pair the master's TOU V2 slot current is the whole group's andslot_current_limits()'s cap can only lower, so a pair is pinned at one inverter's worth; fix shape in open PR feat(solis): write a parallel master's slot current for the whole group (#5556) #5909 (re-probe onupperchange) noted as open. Verifiedslot_current_limits()/CID 7224/7226/min() cap on main.b00dc31b), so the row now states the term is included via the duplicatedmarginal_plan_cost()and carries the keep-in-step rule + the docstring's unstatedmetric_self_sufficiencyexclusion; (b) thePredictioncopies-rates-at-construction trap (prediction.py:195-196 verified) as a new Traps bullet, anchored to the existingpredict_socone.75fc23d9;run_nordpool_test()returns False → counts as PASSED,unit_test.py:1064; verified the runner's truthy-fails-and-aborts loop; TEST_REGISTRY slow flag; octopus.py backend-host query-set facts).eb919801, 2026-10-31), so the entry now carries the fixed-status (mechanism kept for pre-fix(solcast): sum PV calibration day totals unrounded so dull days are not mis-scaled #5802 logs, per the journal's own rule) plus the generalised "grep for dpX-wrapped accumulation" check and the candidate's remaining-sites sweep (fetch.py's dp4 gap-fills, deliberate).test_charge_window_no_source_configured/test_export_window_no_source_configured_raises), the three sources for a TESLA-labelled inverter (Teslemetry automatic_config's own selects / apps.yaml / thetemplates/tesla_powerwall.yamlinverter:block), the case-sensitivity caveat (verified: the raise at inverter.py:569 only fires with noinverter:block, becauseInverter.__init__auto-registers an unknown type as a GE copy otherwise; stock TESLA def verified at config.py:2283). Dropped from the fold: the candidate's transient "permission mode today" paragraph (already covered by the existing trap bullet on permission-mode replay paths).14af9bbb, 2026-10-31); folded into the Gateway MQTT row: the_auto_pv_onlymechanism, the pv_today-counter remainder (deliberate), the symptom split, and theconnected=Falsezeroing incl. listed path + the_check_configured_inverters()comment that remains slot-scoped (still reads "only relied on for an inverter with a slot" on main — true only of that function;_publish_inverter()also zeroes PV-only serials). Verified the merged symbols on main (gateway.py:1845/1296/2288).car_charger_control.py): the raw-dispatch bypass (GH#5807, still open, no fix PR landed — verifiedcharger_control_dispatch_sensor()reads the raw sensor on main whileFetch.car_planned_slot_entity()serves only the planning path; regression source feat(hypervolt): run Predbat-led charging on the shared charger control #5791/6ef9a5e1), theis_chargerprovenance (only Predbat's own Octopus/Kraken sensors publish it), and the planned-slot rule triplicate from fix(car): let control: true filter a charger Octopus drives through octopus_intelligent_planned_slot #5816 with its shared fallback rule (open at review; mixin side PR-only) — both PR-fix(car): let control: true filter a charger Octopus drives through octopus_intelligent_planned_slot #5816-specific facts kept conditional and dated. Inserted after the Hypervolt row.allowedis enforced only inside the string and integer branches ofvalidate_config()'s dispatch (verified on main: exactly twoallowedcheck sites at predbat.py:2054/2093;threadsis the only allowed-user on main and reaches the string branch via"string|integer"); reworded to drop the PR-onlyoctopus_intelligent_deviceexample (not on main).openapi/unsubscription/changecancel topic + PUBACK-reason-code probe trick (PR fix(sigenergy): force the change snapshot on every MQTT connect #5813 merged426ec388), the cross-topic cancel/subscribe race bounded empirically bySIGENERGY_MQTT_RESUBSCRIBE_DELAY= 5 (PR fix(sigenergy): pause between cancelling and re-requesting the change push #5815 mergedb23dbd88), the production listener's MQTT 3.1.1 no-reason-codes blindness and the 28-day settings cache. Both PRs' merged-code state verified on main (sigenergy.py:148/154/249/2153).d1d810dc) but Add optional plan_at to plan_once() to plan at a caller-chosen instant #5811 was superseded by feat(predbat): update_pred can plan at a given instant #5875 (a44e41b), whose merged implementation usestotal_seconds()at every plan-age consumer (predbat.py:829/1456/1526) and documents the future-stamp → "Force recompute due to start of day" (plan.py:2082) one-recompute consequence in theplan_oncedocstring. Nothing to keep — the general.seconds-vs-total_seconds()trap is already journalled (the "timedelta.seconds wraps into [0, 86399]" bullet, which fix(inverter): confirm button presses with total_seconds() so clock skew isn't a failed press #5697 fixed).Existing entries corrected for merges that landed since (step-3 sweep)
eb919801(covered above; the row is otherwise unchanged).15497d83, 2026-11-01 — thresholds nowrate_min_base/rate_max_base, verified in marginal.py on main) — both fixed-statuses written into the same row (queued candidate 5827, out of this slice, should now largely dedup tomorrow).Left queued: 73 candidates (5819 → 5917, plus an issue-5601 note) for later slices. The slice rule (first 15 by filename) was followed; the archive happens daemon-side once this PR is open.