Address maintainer review feedback from zipg on PR #12917:
- [P1] Preserve raw bytes in parse_command_argv returning Vec<Vec<u8>>, pass raw byte slices to redis::Cmd::arg in execute_command, and add target isolation test covering 0x80, 0xff, NUL, UTF-8, and adjacent ASCII.
- [P1] Decode single UTF-8 codepoints by inspecting lead-byte length without consuming adjacent ASCII delimiters in quoteRedisBytes and python template.
- [P2] Group keys by CRC16 hash tag slot in redisDeleteKeysPreview when isCluster=true to prevent CROSSSLOT errors.
* fix(windows): diagnose WebView2 runtime failures and recover startup
On Windows the "main window never appears" failure has three very different
causes that used to share one misleading "enterprise compatibility mode"
retry: WebView2 runtime missing, WebView2 runtime registered but damaged, and
a security product blocking WebView2. This change separates them before Tauri
creates a window and turns the single retry into a bounded recovery ladder.
- webview2_preflight: three-state runtime health (available / missing /
registered_but_damaged), runtime version and install kind, installed security
products, msedgewebview2 process count, Zone.Identifier and integrity level,
plus an STA environment-creation probe with a hard timeout and HRESULT capture
- startup_recovery: 11-profile bounded compatibility ladder (isolated user data,
sandbox/GPU off, RendererCodeIntegrity off for old runtimes, in-process GPU,
temp data, scan delay, warm-up child, AppCompat Windows 8 layer, elevated
relaunch, relocated copy, single-process experiment) with per-profile user data
folders, fast-fail window probing, chain handoff through environment variables,
bounded watchdog and silent auto-remembering of the winning profile
- startup_messages: native-dialog i18n catalog (zh-CN / zh-TW / en, English
fallback); runtime problems point at the Windows 10 offline package that
bundles WebView2, support codes stay in startup.log, success stays silent
- windows_appcompat: reversible per-user AppCompat Windows 8 layer used by a
late profile
- wry: make WEBVIEW2_USER_DATA_FOLDER / WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS
effective at runtime (union --disable-features lists) and honor
WEBVIEW2_BROWSER_EXECUTABLE_FOLDER on any Windows version
- bounded diagnostic logging (runtime health, attempts, stages, HRESULTs) and
DBX_DISABLE_* / DBX_TRY_COMPAT_ON_BROKEN_WEBVIEW2 escape hatches
The standard startup path is unchanged on machines with a healthy runtime.
* test(transfer): initialize target_column_name_case in live Oracle transfer test
The column-name-case feature added a required field to TransferRequest but this
live Oracle test initializer was not updated, so rust-test/rust-fmt-clippy fail on
main as soon as the Rust jobs run (E0063). This is a pre-existing CI blocker for
this PR; keep the fix as a separate commit so it can be split out if preferred.
* test(windows): fix inverted marker assertions and make them version-agnostic
The marker test asserted expected_marker_mismatch(...) == true for the matching
version/profile pair (inverted), and hard-coded 0.6.49 while the marker is scoped
to CARGO_PKG_VERSION (0.6.50 on main). Use the crate version and assert both
directions; this is what failed rust-test on CI.
* fix(windows): preserve existing AppCompat layers and track ownership
* style(windows): keep platform module declarations grouped
---------
Co-authored-by: zipg <4047349+zipg@users.noreply.github.com>
The transparent floating frame (re-enabled on GNOME by default in
6e3afd19f) does not render on GNOME on Xorg: the window is mapped but
stays see-through, and only regions that get damaged (under the mouse,
a focused input) are painted. Reproduced on Debian 13 with DBX 0.6.48.
Only enable the frame by default when GNOME runs as a native Wayland
client, reusing linux_uses_native_wayland(). GNOME X11 falls back to
the opaque window like other desktops; DBX_LINUX_FLOATING_FRAME=1|0
still overrides in both directions.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix(sqlserver): support port in SQL Server host (#12784)
* feat(connection): support SQL Server host with port in ConnectionDialog (#12784)
* style: cargo fmt reflow on sqlserver host-port parsing (#12784)
* fix(sqlserver): preserve invalid endpoint input
* fix(sqlserver): normalize IPv6 endpoints for probes and tunnels
---------
Co-authored-by: zipg <4047349+zipg@users.noreply.github.com>
t8y2