The navbar and the login dialog showed logo2.png, a raster wordmark that
blurred on 2x displays and needed a colour filter to survive the dark theme.
The brand is now the circular icon as SVG with the name as text, so it
renders sharp at every size and takes the navbar's colour in both themes; on
narrow phones the name goes first, then the icon.
The favicon is the SVG with a multi-size .ico fallback, and the PWA-era PNGs,
the tile icon and the Windows installer icon are rendered from the same file.
Without --log-file the viewer said "log printed to console, please see log in
console", which the Windows service, the launchd job and every "log to
console" setup cannot do. The logger now also keeps its last 4 MiB in memory
and the viewer reads that tail when there is no file; the lines carry the
same timestamp and level prefix as the file adapter's.
The log area also gave way to nothing: at 50vh a short window pushed the
filters and the export button below the fold with only a scrollbar to hint at
them. It now shrinks so the footer stays visible.
The installer writes {app}\v2rayA_env.txt with the log file and the asset
directory and points at it with a machine-wide environment variable, then
starts the service — which runs with the Service Control Manager's
environment from boot time and does not see the variable until the next
reboot. Until then v2rayA logged nowhere and looked for assets in the config
directory, and the web log viewer showed only "log printed to console".
When neither the variable nor --win-envfile is given, look for the file where
the installer puts it: the executable's parent directory, then its own.
lucide-static's stylesheet declares eot, woff2, woff, ttf and a legacy SVG
font for all 2112 icons, so Vite copied every format into web/ and the
embedded binary grew from about 26 MB to 48 MB; the SVG font alone is 20 MB of
glyph outlines. The interface uses 44 icons.
A Vite plugin (gui/build/lucide-subset.mjs) scans src/ for icon names — class
usage, icon props, dialog options and the Buefy pack's internalIcons — subsets
lucide.woff2 to those glyphs with subset-font and serves the result as a
virtual stylesheet with the 8 KB font inlined. A name the font does not have
fails the build naming it, where it used to render an empty box.
lucide-static's font CSS references all five webfont formats (eot, ttf,
svg, woff, woff2), so Vite emitted ~23 MB of icon fonts into the web panel;
the SVG font alone was ~20.6 MB. All of them render the same glyphs.
scripts/lucide-font.mjs now regenerates src/assets/lucide-font.css from the
upstream CSS with a woff-only @font-face (woff is supported by every
browser since IE9) and runs automatically via the prebuild/preserve hooks,
so a lucide-static upgrade stays in sync. The build output drops from
~23 MB of font files to a single ~414 KB woff while keeping all icon
classes.
The vendored core/xray submodule is dropped. xray-core is now pinned via a
go mod pseudo-version resolving to v26.7.28 (commit 5ca6f4b7); v26 tags are
not directly resolvable because Xray's module path lacks the /v26 suffix, so
the pin must be made by commit hash. CI workflows and the AUR PKGBUILD no
longer need "submodules: recursive" / "git submodule update".
The juicity and tuic outbounds are ported from softwind to
github.com/daeuniverse/outbound (temporarily replaced with an olicesx fork
pending sticky-ip support):
- Dialer calls use DialContext; the network string is decoded with
netproxy.ParseMagicNetwork instead of a "udp" prefix check, since it may
be binary-encoded via netproxy.MagicNetwork.
- A packetConnAdapter wraps xray's UDP dial result: outbound asserts the
underlay conn to netproxy.PacketConn whose ReadFrom/WriteTo signatures
(netip.AddrPort / string) differ from net.PacketConn, while xray returns
*internet.PacketConnWrapper.
The backend now reports an up-to-date list as a result, so the dialog shows an
info toast with the version rather than "could not update GFWList: … is up to
date".
Three endpoints answered FAIL for something the caller asked for and got:
- an up-to-date GFWList came back as "could not update GFWList: latest version
is …. GFWList is up to date", because the check returned an error;
- deleting the GFWList when it was already gone returned the raw
"remove …: no such file or directory";
- the update check said "failed to get latest version from Package file: 1".
The up-to-date case is now a sentinel error the controller turns into a
success carrying alreadyUpToDate, deleting what is already gone succeeds, and
the two package-index messages say what was missing. "which can not be nil"
also became a sentence about the request.
A rule that sends a name to a local resolver which forwards back to v2rayA
makes the two exchange the same query until one of them runs out of memory;
v2rayA/v2rayA discussion #1950 reproduces it with dnsmasq on OpenWrt. The
firewall-level self-redirect is already handled by the 0x80 mark, but nothing
saw the loop at the resolver level.
Every query this process sends upstream carries a random per-process token in
an EDNS0 local option. A query that arrives carrying that token has come back
around such a loop and is answered with SERVFAIL, with one log line per ten
seconds naming the question and how many were refused.
The README pointed at an image host upload from April 2020 showing an
interface that no longer exists. The new pair lives in the repository, so it
cannot disappear, and the dark one is served to readers whose system asks for
a dark theme.
A virtual scroller needs one fixed row height, so every log line was clipped at
the screen edge and a phone showed a column of timestamps with no messages. On
a narrow screen the tail is rendered plainly with the lines wrapped, and the
header says how many older lines are hidden.
The About text also still pointed at the issue tracker, which upstream has
closed in favour of discussions.
A DNS or connection failure produced "Could not download the asset from
api.github.com (HTTP )" in the GUI, because the localized message always
rendered an HTTP status and there was none. Unreachable hosts now use their own
code with the innermost reason, so the user sees the DNS or connection error
instead of an empty pair of brackets.
Auth recovery reloads the page, so nothing ever filled the queue and nothing
called its retry function; the two modal imports it needed were unused too.
Also read the token with getItem instead of hasOwnProperty on localStorage.