[DEBUG] Minimal fix: TypeScript API + detect open handles

[sfreudenthaler]

Purpose

Minimal, surgical fix to identify the root cause of Frontend Unit Tests timeout (~20 minutes).

Strategy

Changed ONLY what's absolutely necessary:

1. ✅ Fix TypeScript compilation errors (tests won't run without this)
2. ✅ Add --detectOpenHandles flag to see what's leaking

Intentionally NOT changing:

• ❌ Jest configuration (testTimeout, maxWorkers)
• ❌ GitHub Actions logging
• ❌ --forceExit flag (want to see real failure)

Changes

TypeScript API Fixes (Required)

// core-web/libs/data-access/src/lib/dot-router/dot-router.service.ts
- const nav = this.router.currentNavigation();
+ const nav = this.router.getCurrentNavigation();

// core-web/apps/dotcms-ui/src/app/api/services/guards/ema-app/edit-page.guard.ts
- const url = router.currentNavigation().extractedUrl.queryParams['url'];
+ const url = router.getCurrentNavigation().extractedUrl.queryParams['url'];

Leak Detection (Debug Only)

<!-- core-web/pom.xml -->
<arguments>nx affected -t test --base=origin/main --exclude='tag:skip:test' -- --detectOpenHandles</arguments>

Expected Output

Based on previous debug run showing:

A worker process has failed to exit gracefully and has been force exited.
This is likely caused by tests leaking due to improper teardown.
Try running with --detectOpenHandles to find leaks.

We should now see:

Jest has detected the following X open handle(s) potentially keeping Jest from exiting:

  ● TIMEOUT/TCPWRAP/etc

      at libs/some-library/some-file.spec.ts:123:45

This will tell us EXACTLY which test file and line is leaking resources.

Testing Plan

1. Monitor "Frontend Unit Tests" job
2. Look for "Jest has detected" messages in logs
3. Identify specific test files causing leaks
4. Fix those specific tests in a follow-up PR

Previous Attempt

Closed #34191 - made too many changes at once, harder to debug.

Related: #34166

[sfreudenthaler]

Fixed Command Line Parsing Issue

The error was NOT related to the TypeScript API fixes - those are required.

The Problem

The Maven command had syntax issues:

<!-- BROKEN -->
<arguments>nx affected -t test --base=origin/main --exclude='tag:skip:test' -- --detectOpenHandles</arguments>

Yarn was parsing this as:

nx affected --detectOpenHandles  # Missing all the other arguments!

The Fix

<!-- FIXED -->
<arguments>nx affected -t test --base=origin/main --exclude=tag:skip:test --detectOpenHandles</arguments>

Removed:

• Single quotes around 'tag:skip:test'
• The -- separator before --detectOpenHandles

Why Keep the TypeScript Fixes?

The currentNavigation() → getCurrentNavigation() changes are real compilation errors that prevent tests from running at all. Without them, you get:

error TS2551: Property 'currentNavigation' does not exist on type 'Router'.
Did you mean 'getCurrentNavigation'?

Tests should now run properly with --detectOpenHandles showing us which tests leak resources.

[sfreudenthaler]

Update: Added --forceExit Flag

What Happened

The previous run with only --detectOpenHandles hung indefinitely at 22:08:26 GMT.

Why It Hung

--detectOpenHandles makes Jest wait forever for open handles to close before reporting. Since the handles never close (that's the bug!), Jest never completes.

The Fix

Added --forceExit flag:

<arguments>nx affected -t test --base=origin/main --exclude=tag:skip:test --detectOpenHandles --forceExit</arguments>

How these work together:

• --detectOpenHandles = Detect what resources are leaking
• --forceExit = Force Jest to exit and show the detections

What to Expect Next

Tests will now:

1. ✅ Run to completion (instead of hanging)
2. 📊 Show us which specific test files have open handles
3. 📝 Print messages like:

   Jest has detected the following X open handle(s):
   
     ● TIMEOUT
   
         at libs/edit-content/src/lib/some.spec.ts:147:9
   

This will tell us exactly which tests need to be fixed.