chore: Release release/2026-W35 - #7278
Open
github-actions[bot] wants to merge 602 commits into
Open
Conversation
fix(server): Use `query.run()` to get servers
bench reads this key to warn before commands that desync the container from the Bench and Site records it mirrors. common_site_config is the only bench config bind-mounted into the container, so the marker has to live here rather than in bench_config. Existing benches pick it up as their groups redeploy, since a deploy creates a new Bench rather than mutating the current one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
fix(ui): Make billing overview page responsive
feat(bench): Mark managed benches in common_site_config
fix(mpesa): Validate with service
fix(2fa): Skip alerts for disabled teams and users
libatspi.so.0 is a hard DT_NEEDED of headless_shell, but the package was spelled ibatspi2.0-0. It only resolved because apt falls back to POSIX regex matching for names containing a dot — one rename away from every Chrome PDF breaking with no obvious cause. libdbus-1-3, libexpat1, libglib2.0-0 and libudev1 are linked too, but were only present transitively via weasyprint/wkhtmltopdf/util-linux. Listed them explicitly so dropping an unrelated package can't break PDFs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
fix(billing): Add usage record to own team
Misc fixes
fix(stripe): Always pass payment method while creating invoice
fix(client): Separate readable fields from editable ones
The root collected CSV exports, partial database dumps, and nginx backups from debug sessions. Every one of them showed in `git status`, which makes the real changes hard to see. The dumps also carry customer data, so they must never reach a commit by accident. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
An agent that opens this repo has no way to tell what `arm-builds`, `debugging`, or `deployment` hold, and `press/` has 27 subdirectories with no map. Each README says what the directory is for and how to run it. `press/README.md` carries the subdirectory table, because that is where the guesswork costs the most time. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
These four files load into the context of every agent session, so an ambiguous sentence costs on each run. The rules now follow ASD-STE100: short sentences, active voice, no contractions, and no semicolons. The rules themselves do not change. Only the sentences do. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The README told the reader to configure the proxy in `proxyOptions.js`, which no longer exists. The `frappeui` plugin in `vite.config.ts` sets `frappeProxy: true` and does the same work. The README also named Feather for the icons, but the same plugin sets `lucideIcons: true`. Added the build output paths, and rewrote the prose in simple english. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
docs: Make the repo readable for agents
fix(invoice): Set Amount due as zero once paid
fix(ui): Make a single command for ssh access dialog
fix(ui): Keep whitelisted methods on the bench dropdown's group resource
The chart read `mysql_up`, a gauge of 0 or 1. Prometheus takes one sample per step, so an outage between two steps was invisible. For a 7 day range the step is 4 hours, so almost every outage was lost. The query now averages the gauge over each bucket. Each point is the percent of that bucket that MariaDB was up. The y-axis also keeps off zero, else a drop from 100% to 91% stays flat at the top of the plot. This is opt-in per chart, because CPU and memory need the zero baseline. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
fix(server): Show database uptime as a percent of each bucket
BarChart carried the drag-to-zoom setup inline. LineChart needs the same behaviour, so the setup moves to useDataZoom, which the chart gives a function to turn an axis value into a date. The event shape is now read as `event.batch?.[0] ?? event`. A category axis reports the picked range in a batch, a time axis reports it on the event itself. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The site charts let you drag over a chart to narrow the time range. The server charts did not, so a spike found on the CPU chart had to be followed by hand with the duration select and the two pickers. LineChart now emits the picked range, and every chart on the tab, line and bar, sets the range to it. The refetch is debounced by 500ms because one drag can end in more than one zoom event, and each chart on the tab refetches when the range changes. The zoom cursor is armed on the first `finished` render. Before that the toolbox drops the action. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The site charts had drag to zoom on the bar charts and on uptime only. The line charts above them, usage counter, requests, requests CPU usage and the two background job charts, did not have it, because LineChart did not emit the event. It does now, so each chart needs one listener. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Setting the duration to custom let its watcher fill a default one hour range. The dragged dates were assigned only after the next tick, so every chart on the tab could fetch the default range first and the dragged range after it. The watcher is sync now, so the three assignments settle before any chart reads them, and the handler no longer waits a tick. The test asserts one request per chart after a drag. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
feat(dashboard): Add drag to zoom on the server and site line charts
github-actions
Bot
requested review from
Aradhya-Tripathi,
adityahase,
balamurali27,
prathameshkurunkar7,
shadrak98,
siduck and
tanmoysrt
as code owners
August 24, 2026 04:52
Contributor
|
@github-actions[bot], thanks for the contribution, but we do not accept pull requests on a master. Please close this PR and raise PR on an develop branch. |
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
11 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.
Weekly release PR