Repository navigation
[pull] main from jason5ng32:main - #25
Merged
Merged
Conversation
A single slow Radar segment used to fail the whole request with a 500 and log an error at every catch layer. Segments are now fetched with Promise.allSettled: failed ones degrade to missing fields (the response pipeline already tolerates sparse data), and each request logs at most once — warn on partial failure, error only on a full wipe-out. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Raw mtr text was hard to scan and useless on mobile. Parse each probe's output (header-driven column mapping, tolerant of differing mtr builds) and render a compact table: adaptive Host/IP/ASN identity columns plus whatever numeric columns the data carries; falls back to the raw text when nothing is parseable. Table headers localized in all four locales. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Foundation for the shareable network-diagnosis report: a versioned, whitelist-style schema shared by both halves (frontend builds payloads, backend will validate untrusted POST bodies against the same specs), plus data-level IP tail-masking for the privacy option. Free-form text cannot enter a report — every field is typed, enum'd or length-capped. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Every "my network" test now emits a <domain>:finished event with its complete structured result on the app bus (existing thin events keep their fields — achievement rules are untouched). Connectivity and WebRTC additionally record locale-free status/NAT enums next to their localized labels so downstream consumers never parse t() output. A collector mounted once in App.vue normalizes each payload through per-section builders (shape-based cleaning, no free text) and keeps the latest schema-valid snapshot per section for the share dialog. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
POST /api/report validates an untrusted report against the shared schema whitelist (free text cannot enter storage), caps it at 32KB and writes it to Workers KV under a 128-bit unguessable id with a user-chosen TTL (1/7/30 days); GET /api/report/:id serves the read-only report page and AI agents, behind a short edge cache since reports are immutable. The whole feature is env-gated on the three CLOUDFLARE_* variables and surfaced to the frontend as configs.reportSharing. Rate limiting is deliberately left to the deployment layer (edge rules / the env-gated global /api limiter), not the handler. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
New dock entry opens the diagnostic-report dialog: pick collected sections (original-site-only tools hidden for self-hosts), optionally mask IP tails, preview exactly what leaves the device, then export — a KV-backed /r/:id link (TTL 1/3/7 days, default 1; the backend forces out-of-whitelist values down to 1 day), a self-describing Markdown prompt for AI assistants, or a JSON download. Copy localized in all four locales. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The share link now lands somewhere: a noindex page that fetches the
stored report and renders every section in the viewer's own language
(payloads hold locale-free enums only), with provenance, expiry and
staleness callouts plus copy-for-AI. IPCheck.ing-source cards carry
their signed-in enrichments (proxy verdict, line type, ASN-geo match,
quality score) through the whole pipeline — 'unknown' verdicts and
sign-in-gated values never enter a report. Stored values gain an
{ expiresAt, report } wrapper so readers can show the deletion time,
and the size ceiling now fits real full runs (256KB report cap, 1mb
body limit — a complete test sweep serializes near 100KB).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Closing pass over the diagnostic-report feature: the privacy policy gains a feature-gated "shared diagnostic reports" section in all four locales (and the "we do not keep results on our servers" claim is qualified accordingly); connectivity status codes move to a single shared constant so the component, builder whitelist and schema enum can't drift apart; the report page and speed-test copy get display polish; the KV read path drops its pre-launch legacy fallback and the express body limit documents its relationship to REPORT_MAX_BYTES. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This branch had an error being deployed
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )