[GH-ISSUE #1585] fix(ci): restore formatting gate after ADB schema repair #532

New issue

Closed

opened 2026-10-15 18:25:57 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-15 18:25:57 +00:00

Owner

Originally created by @N0zoM1z0 on GitHub (Oct 10, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/1585

Current main cca7bf0022ad8d4f5812d9185d21f749b26c4296 fails the repository formatting gate in src/domain/adb/adbDeviceAnalysis.ts after the CI repair. Reproduced in an isolated branch/worktree with the pinned toolchain:

npm run format:check

The formatter names that one file. A direct oxfmt src/domain/adb/adbDeviceAnalysis.ts --check reproduces the same failure. The latest following commit 6543405252d7c740c87a3bb433cf666187af41fa changes portable regex patterns in that file; recheck its formatting and apply the repository formatter as needed.

Expected: npm run format:check passes without changing ADB schema semantics. Discovered while validating #1369. No matching open issue or focused PR was found via GitHub search.

Originally created by @N0zoM1z0 on GitHub (Oct 10, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/1585 Current main `cca7bf0022ad8d4f5812d9185d21f749b26c4296` fails the repository formatting gate in `src/domain/adb/adbDeviceAnalysis.ts` after the CI repair. Reproduced in an isolated branch/worktree with the pinned toolchain: ```sh npm run format:check ``` The formatter names that one file. A direct `oxfmt src/domain/adb/adbDeviceAnalysis.ts --check` reproduces the same failure. The latest following commit `6543405252d7c740c87a3bb433cf666187af41fa` changes portable regex patterns in that file; recheck its formatting and apply the repository formatter as needed. Expected: `npm run format:check` passes without changing ADB schema semantics. Discovered while validating #1369. No matching open issue or focused PR was found via GitHub search.

bsakaguchi

2026-10-15 18:25:57 +00:00

closed this issue
added the
area: runtime

bug
labels

bsakaguchi commented

2026-10-15 18:25:57 +00:00

Author

Owner

@N0zoM1z0 commented on GitHub (Oct 10, 2026):

Follow-up on the latest main: 6543405252d7c740c87a3bb433cf666187af41fa already restores the affected file formatting as part of its portable regex correction. Reproduced the failure on cca7bf00, then integrated 65434052 in the isolated review branch and reran the direct formatter check: exit 0, no changes required. The latest-main successful receipt is retained. Closing as fixed by that main commit; no redundant formatting patch is needed.

@N0zoM1z0 commented on GitHub (Oct 10, 2026): Follow-up on the latest main: `6543405252d7c740c87a3bb433cf666187af41fa` already restores the affected file formatting as part of its portable regex correction. Reproduced the failure on `cca7bf00`, then integrated `65434052` in the isolated review branch and reran the direct formatter check: exit 0, no changes required. The latest-main successful receipt is retained. Closing as fixed by that main commit; no redundant formatting patch is needed.

bsakaguchi referenced this issue

2026-10-15 18:28:32 +00:00

[GH-ISSUE #2383] [Tracker] Audit analysis and debugging coverage for the TIOBE top 100 languages (October 2026) #794

bsakaguchi referenced this issue

2026-10-16 21:13:46 +00:00

[PR #532] [MERGED] fix(native): retain lazy dylibs, normalize version-min builds, limit thread entrypoints #2053

bsakaguchi referenced this issue

2026-10-16 21:13:48 +00:00

[PR #534] [MERGED] fix(native): match compound otool keys exactly and badge unknown thread entrypoints #2056

bsakaguchi referenced this issue

2026-10-31 00:39:44 +00:00

[GH-ISSUE #5551] [Bug] trace-dylib-resolution omits lazy dylib dependencies while reporting complete coverage #3379