Skip to content

docs(debug-journal): fold the 2026-10-31..11-08 queue slice (14 of 15 candidates); consolidate the largest areas - #6058

Merged
springfall2008 merged 1 commit into
mainfrom
bot/debug-journal-2026-11-09
Nov 9, 2026
Merged

springfall2008 merged 1 commit into
mainfrom
bot/debug-journal-2026-11-09

Conversation

@springfall2008

Copy link
Copy Markdown
Owner

Automated journal-update run (2026-11-09), folding the 2026-10-31–11-08 queue slice. I read the journal end to end, verified every candidate against current main (9947c0d), re-checked entries against the merges since the last fold, ran run_pre_commit (hooks + quick suite green, 5 slow skipped), and left the file at 161.5KB (was 156.4KB). 99 candidates remain queued. Per-candidate and per-correction detail below.

Candidates — 14 folded, 1 dropped, 99 left queued.

Folded:

  • GH#5889 (31 Oct) — folded by sharpening the GH#4445 bullet under Plan: charging and holding: a charge window whose target is at/below the modelled SoC charges nothing but pins the reserve (prediction reserve-pinning), and the label is a knife-edge — HoldChrg requires the min SoC over the window at/above the limit, so such windows fall back to generic "Planned Charge". Verified the output.py rule and the prediction.py reserve-pinning on main plus the reporter's own plan/log.
  • GH#5890 (31 Oct) — folded into the GH#5219 entry (curve area): a register-wired battery_rate_max reading a literal 0 W float defeats the ≤0 W fallback (it reads the same broken register), and a restart mid-incident clears the saved curve so a ZeroDivisionError starting long after the trigger means look for a restart between; a crashed run never saves a curve, so repeats recurse. Verified the autodetect gate on main; fix PR fix(inverter): treat a 0W live rate limit as unset, so Predbat's own 0W write cannot latch the rate at 0 (#5219) #5626 still open.
  • PR fix(debug): write numpy values as plain numbers so debug dumps load #5892 (31 Oct, merged b7fa199) — the candidate was "update the entry once merged"; the entry already credited the fix, sharpened it with the dumper fact (new dumps carry plain numbers; the loader constructor replays tagged old dumps).
  • GH#5893 (31 Oct) — folded as the durable class fact under SolaX: realtime payloads carry explicit nulls, so dict.get(key, 0) defaults are inert; PR fix(solax): treat a null battery chargeDischargePower as 0 in the plant sum #5894 (merged) + the sibling guards. The candidate's not-yet-fixed siblings are no longer live on main (the batterySOC/batteryRemainings/batteryTemperature guards changed shape on main); the candidate's "check the siblings" grep recipe is what survived, with float(ratedPower) noted as the one shape still unguarded (device-list null, suspect).
  • GH#5895 (31 Oct, merged f407d36) — folded at its post-fix(web): show the current value at the top of the /entity history table at once #5913 state (039e7c5, also merged): the /entity history-table display model, as one bullet under Web, MCP and Chat, and updated the GH#5509 dump-reading bullet with the *_today arrays' minutes-ago convention.
  • GH#5896 (2 Nov, merged db97964) — folded by sharpening the io_confirmed_credit bullet under Car charging and Intelligent dispatch: PV10's dispatch-gone hedge is skipped for confirmed minutes in both engines (verified prediction.py + the kernel mirror, parity 19); a dump with non-empty io_confirmed_credit scores PV10 kinder than the fix(octopus): model a vanishing IOG dispatch for octopus_intelligent_slot users #5304-era math.
  • GH#5901 (1 Nov, two candidates) — folded as one bullet under Check configuration before code: the pre-charge config trio (rate_low_threshold manual cap, combine_charge_slots, set_export_freeze_only), the sale-cap arithmetic, and that additive event boosts can never move a min-rate scan. The maintainer's bug reclassification is noted in the PR body only (per-issue narrative stays out of the journal).
  • GH#5902 (1 Nov) — folded into the GH#4445 bullet (row "target" = predicted end SoC, check via best_charge_limit/status_detail) and a new Replays bullet: the dump's rate tables sit back-to-back, grep each ^rate_ key's line bounds before extracting.
  • GH#5904 (1 Nov) — folded as one bullet under Sensors, history and load data: History columns replay recorded *_today sensors and the empty-slot glyph is == 0 after dp2, so ~20 W-equivalent counter ticks render as 0.01–0.02.
  • PR Redistribute fleet target split when an inverter has no room, split exports by export rate (#4856 F2) #5906 (1 Nov, merged 3f07cf1) — folded as a correction (below) plus the rate weighting fact in the GH#5219 entry.
  • PR Redistribute fleet target split when an inverter has no room, split exports by export rate (#4856 F2) #5906 review (test conventions, 2 Nov) — folded under Traps → Tests: run_execute_test() inherits fleet count and reserve semantics from the previous scenario.
  • PR fix(gateway): five follow-ups from the Hub live display review #5911 (merged e8c75e6) — folded under Gateway MQTT: the display-bindings publisher bypasses _publish_raw() deliberately (display-mode block), run() ordering carries screen-off revocation, and gateway test fakes of _publish_raw must return True + seed _last_oversize_warn (verified against test_gateway.py fakes).
  • GH#5912 (2 Nov, template regex drift; PR feat(templates): ship octopus_free_session in the Tesla and four other templates (#5912) #5931 merged a732d08) — folded under Octopus: check the user's template's session regex lines first; some still ship pre-v19 patterns (hanchu_cloud, ep_cube_cloud verified still carrying them) and the shipped test only pairs saving+free lines.

Dropped:

Corrections to existing entries (each invalidated by a merge since the last fold):

Consolidation (file was past the ~150KB threshold at 156.4KB):

🤖 Generated with Claude Code

… candidates); consolidate the largest areas

Co-Authored-By: Claude Code <noreply@anthropic.com>
@springfall2008
springfall2008 marked this pull request as ready for review November 9, 2026 08:20
@springfall2008
springfall2008 enabled auto-merge (squash) November 9, 2026 08:20
@github-actions github-actions Bot added the BOT_REVIEW Trigger an autotriage label Nov 9, 2026
@springfall2008
springfall2008 merged commit cabf471 into main Nov 9, 2026
7 checks passed
@springfall2008
springfall2008 deleted the bot/debug-journal-2026-11-09 branch November 9, 2026 08:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

BOT_REVIEW Trigger an autotriage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant