Issue Review: cloudflare/workers-sdk#7244

Summary

Feature request for debugging tools to diagnose hanging tests in vitest-pool-workers.

Findings

• Created: 2024-11-12
• Updated: 2025-10-30
• Version: Not specified (issue is version-agnostic feature request)
• Component: vitest-pool-workers (current version: 0.12.6)
• Labels: bug, enhancement, vitest
• Comments: 0

Key Evidence

1. Issue Description: User requests a debug flag or tooling to help diagnose where tests are hanging after switching from Jest to the Vitest integration. They report sporadic hangs with no error output.

2. Related Fix Found (PR #11681): A specific hanging scenario was fixed in December 2025:

   • "Fix vitest-pool-workers hanging when the default inspector port (9229) is already in use"
   • This is a targeted fix for one hanging scenario but does NOT address the broader feature request for general debugging tools

3. No General Debugging Feature Implemented: The changelog shows no new debugging flags, diagnostic modes, or tools for identifying the source of hanging tests have been added.

4. Feature Request Still Relevant: The request for tooling to debug hanging tests (e.g., a debug flag showing current test state, timeout diagnostics, or similar) has not been addressed.

5. Zero Engagement: No comments, no assignee, no linked PRs referencing this issue directly.

Recommendation

Status: KEEP OPEN

Reasoning: This is a valid feature request that remains unaddressed. While PR #11681 fixed one specific hanging scenario (inspector port conflicts), the broader ask for debugging tools to diagnose arbitrary test hangs has not been implemented. The request for a debug flag or similar tooling to identify where tests are hanging is still a valuable feature gap.

Action: Keep open as a valid enhancement request. Consider adding to backlog for future prioritization. The lack of engagement (0 comments) suggests it may benefit from triage to determine priority and scope.

Suggested Comment

This feature request is still relevant. While PR #11681 fixed a specific hanging scenario related to inspector port conflicts (released in v0.12.0), the broader request for debugging tools to diagnose arbitrary test hangs remains unaddressed.

Is there any update on plans to add debugging capabilities (such as a debug flag or diagnostic output) to help identify where tests are hanging? This would be valuable for users experiencing sporadic, hard-to-diagnose test hangs.