8000 [pull] main from jason5ng32:main by pull[bot] · Pull Request #29 · comanche2008/MyIP · GitHub
[go: up one dir, main page]

Skip to content

[pull] main from jason5ng32:main - #29

Merged
pull[bot] merged 59 commits into
comanche2008:mainfrom
jason5ng32:main
Aug 14, 2026
Merged

pull[bot] merged 59 commits into
comanche2008:mainfrom
jason5ng32:main

Conversation

@pull
@pull pull Bot commented Aug 14, 2026 •
Copy link
Copy Markdown

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 : )

jason5ng32 and others added 30 commits July 30, 2026 18:05
Bare .pipe() left upstream body errors unobserved: a reset after headers
could crash the process, and client disconnects kept the upstream fetch
running. Await stream/promises pipeline() so errors propagate both ways,
treat premature-close as a routine client abort, and fall back to the
500 JSON response only while headers are still unsent.

Closes #363

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Extension- or translator-injected cross-origin stylesheets make
html-to-image's webfont embedding throw while reading cssRules, which
silently broke the whole save-image flow for affected visitors. The live
page has already loaded its fonts, so retrying once with skipFonts
renders an equivalent capture.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The v7 storage key has been live long enough that migrating from
userPreferences_v6 / userPreferences no longer pays for its complexity.
All readers (store bootstrap, i18n language pick, the locale-preload
head script) now touch only the current key; visitors from that era
simply restart from defaults, and stale legacy entries are inert.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Routine minor/patch bumps (vue 3.5.41, vite 8.2, sentry 10.69, firebase
12.17.1, …) plus @tanstack/vue-table 8 → 9; pnpm 11.20. Vue 3.5.41
packages allow-listed in the workspace minimumReleaseAge exclusions.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Latest copy-in: forwarded props via useForwardProps/reactiveOmit,
String|Number tab values, asChild/as passthrough, refreshed classes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The Connectivity grid's add tile now opens a tabbed dialog: import one
of 11 curated lists (Iran / Russia / China country packs + AI, social,
streaming, gaming, developer, cloud, crypto, news themes — 130 sites)
or hand-add a custom test. Imported members materialize into the
customConnectivityTargets preference tagged with their listId, so cards
are individually removable and a list can be removed as a whole from
the dialog; hostname dedupe and a shared 60-target cap apply on import.

Cards (built-in included) now show real site favicons served from
committed 64px PNGs under public/favicons/ — same-origin, so icons
render even when the tested site is blocked for the visitor; a data
test enforces one PNG per member, and the static server caches the
directory for 30 days (a changed icon ships under a new id/filename).

Also, since the section was reworked in the same change:
- multi-round mode now runs on manual/section refreshes too — it was
  boot-only, so visitors with connectivity auto-run off could never
  trigger rounds at all
- shared report caps grow 24 → 72 targets so reports carry every
  tested target instead of a silently truncated subset
- dead ServiceStatusBanner leftovers (logic + locale keys) removed;
  the banner UI itself was retired earlier

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jason5ng32 and others added 27 commits August 10, 2026 13:38
On refresh, boot events (ipinfo:finished and friends) could beat
/api/getuserinfo, so the engine evaluated the already-achieved guard
against the all-false initial state and re-toasted / re-reported badges
the account already holds. Rules matched before the snapshot applies now
park in a pending set and are re-checked once User.vue flips the new
userAchievementsSynced flag; as a side effect, pre-sync events are no
longer silently lost.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sixteen festival statuses join the composer, window-gated on the
visitor's local date: fixed-date festivals recur via yearly MM-DD
rules (zero maintenance), lunar-calendar ones (lunar/diwali/eid)
carry explicit windows through 2031 — the data test starts failing
90 days before that runway ends as the refresh reminder. Status
vocabulary moves to data/pulse-statuses.js, shared with tests; the
pulse backend mirrors the same windows with a wider grace.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Clicking a status now plays a canvas particle celebration in the Sheet:
emoji pop by default, fireworks / falling sprites on mapped festival
statuses. A local send gate mirrors the backend rate limit — re-clicking
the sent status replays the animation freely, switching inside the
cooldown short-circuits to the rateLimited hint without hitting the
network.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
New /api/outages merges Cloudflare Radar verified outages and traffic
anomalies (30d window, anomaly-vs-outage dedupe, ongoing-first ordering,
1h edge cache); the Pulse Sheet renders them as a bulletin card list
with cause/level translated in all four locales.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
"Ended" describes the record; "Recovered" describes the network. Synced
across all four locales, plus the zh ongoing/started wording.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Both Pulse widgets hand-rolled their own Intl.RelativeTimeFormat call;
they now go through utils/relative-time.js, which also owns the outage
duration formatter.

Two output fixes come with the move: the relative style goes from narrow
to short, so French and Russian read "il y a 3 min" instead of a bare
"-3 min", and numerals no longer touch CJK units ("3 小时前").

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…lures

Private, loopback, link-local and other reserved addresses carry no
registry record, so an RDAP or WHOIS lookup for one can only fail. A
shared isPrivateIP() in common/valid-ip.js now gates both the handler
and the tool, so a visitor pasting a LAN address gets an answer instead
of a 500 — and we stop spending an upstream call to earn it.

On the frontend a 4xx from /api/whois renders as UI copy rather than a
console error: an unsupported TLD or an unregistered domain is a normal
outcome, not a failure. Only 5xx still reports.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Every IP form in the project feeds an external lookup, so the useful
question is "can anyone out there answer about this address" rather than
"is this private". isPrivateIP becomes isUsablePublicIP, with validation
folded in — a string that isn't an IP isn't a usable one either.

The IPv6 side was enumerating reserved prefixes and left holes: the whole
unassigned 4000::-fbff:: span read as public, as did Teredo, 6to4,
ORCHIDv2 and the 3fff::/20 documentation block added in 2024. Global
unicast only ever comes from 2000::/3, so testing that range plus its
carve-outs is both shorter and complete.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
QueryIP, MtrTest and GlobalLatencyTest all took any well-formed IP and
spent a round trip discovering that nobody can answer for it: a LAN
address walks every geo source collecting the same "no data", and no
Globalping probe has a path to one from any country.

All three now answer locally. The two Globalping tools share
classifyTarget(), which returns empty / invalid / unreachable / ok so the
input can both style itself and say why a well-formed address was
refused — a silently greyed-out Run button reads as a bug. QueryIP also
drops its error message once the box is emptied, since the complaint no
longer describes anything on screen.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The seven geo routes let a reserved address through to their upstream,
which could only answer "no data" — a visitor querying their own LAN IP
cost a real API call at every source. requireValidIP tightens into
requirePublicIP and rejects that address before the handler runs, so
geo-handler, maxmind and ipcheck-ing need no check of their own; the
guard was already their sole validation layer.

Malformed input and reserved space keep distinct messages — the two
failures point at different fixes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…nates

Every geo route now returns an IANA zone name, added on the way out by the
withTimeZone() middleware rather than by any handler — including the private
API pass-through, which needs no new upstream field.

The zone is derived from the latitude/longitude the response itself carries,
not from a second lookup of the same IP. Asking another database would
eventually place the address elsewhere and print a zone that contradicts the
city next to it. Coordinate accuracy measured against MaxMind's own time_zone
over 30k sampled addresses: 99.80% exact, 99.98% correct offset; the rest are
neighbouring zones across a land border that share an offset anyway.

Only the name ships. Geo routes sit behind a 24h edge cache, so a cached UTC
offset would be an hour wrong for everyone between a DST switch and the
entry's expiry — the frontend renders the offset per view instead, reusing
the formatter the analytics path already had.

The field travels the full report path: event payload, builder, schema (as a
typed timeZone kind, not a free string), the /r/:id table, the Markdown
export and the JSON download.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…nner

Sources become self-describing { id, name, run() } providers; index.js
walks each card's fallback chain through runChain, gating every hop with
isValidIP so a garbage upstream response now falls through to the next
source instead of ending the chain.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@pull pull Bot locked and limited conversation to collaborators Aug 14, 2026
@pull pull Bot added the ⤵️ pull label Aug 14, 2026
@pull
pull Bot merged commit e01c77d into comanche2008:main Aug 14, 2026
1 check passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0