A handful of orgs still have realtime bandwidth tracked outside the
bandwidth resource (not billed/rolled in yet). Earlier commit hid
their realtime value entirely once the breakdown bar suppressed it.
Render a standalone informational Realtime bandwidth row only when
realtimeBandwidthValue > bandwidthValue, matching today's pre-merge
behaviour for those orgs while keeping the modern path one row.
A handful of legacy orgs have realtime bandwidth tracked separately
(not yet billed and not added into the bandwidth resource). For them
realtimeBytes > totalBytes, which would otherwise overflow the bar or
collapse the regular segment to zero. Detect that case and render
bandwidth as a single segment instead, preserving today's behaviour
for those orgs.
Backend already rolls realtimeBandwidth value + amount into the
bandwidth resource, so the previous commit was summing them again
(value + amount), inflating both the displayed total and the priced
amount, and over-driving the progress bar.
Use bandwidth?.value / bandwidth?.amount directly (already include
realtime). For the multi-segment progress bar, carve the realtime
slice out of the total instead of summing — regular = total - realtime,
realtime = realtime — so the segments add to the actual bandwidth
total. Same neutral colour family as before, no multi-colour added.
Clamps realtime to [0, total] in case of dirty data.
mounted is now only set to true on successful load. On error, it stays
false so the $effect never fires, activeScopes stays empty, and the
parent-bound scopes prop is never overwritten with [].
Parameters with a non-empty example value are treated as required when
the provider is enabled. Params without an example (e.g. GitLab endpoint
for self-hosted) remain optional regardless of enabled state.
Previously a rejected API call left allScopesList empty and mounted
stuck at false with no feedback to the user. Now catches the error,
displays an inline alert, and sets mounted in finally so the component
settles cleanly.
Merges the standalone "Realtime bandwidth" row into the "Bandwidth" row.
The progress bar now renders two color-coded segments — regular bandwidth
and realtime bandwidth — with hover tooltips showing the realtime value.
Stop unnecessary API calls on usage routes that no longer render
anything. Replace each loader with an empty return and remove
leftover export let data bindings from the page components.
The *Total fields returned by the API represent all-time entity counts
(databases, buckets, files, deployments) that do not change with the
selected date range. Showing these alongside period selectors caused
customer confusion when comparing against billing stats.
- Remove Usage tab and page content for functions, sites, and storage
sections where only all-time counts were displayed
- Keep databases usage page with reads/writes (period-specific)
- Keep individual function usage page with executions and GB hours (period-specific)
- Fix typo in function header tab event name (sage -> usage)
Harsh Mahajan
harsh mahajan
Chirag Aggarwal
Damodar Lohani
Damodar Lohani
abhay-dev2901
Claude