move address family socket creation to inside of try catch

[adhami3310]

No description provided.

[codspeed-hq]

CodSpeed Performance Report

Merging #5637 will not alter performance

_{Comparing move-address-family-socket-creation-to-inside-of-try-catch (929ffc3) with main (00cdc4d)}

Summary

✅ 8 untouched benchmarks

[greptile-apps]

Greptile Summary

This PR improves the robustness of socket handling in the _can_bind_at_any_port function within reflex/utils/processes.py. The change moves socket creation inside the existing try-catch block, ensuring that both socket creation and binding operations are protected by exception handling.

Previously, only the sock.bind() operation was within the try block, while socket.socket() was called outside of it. This created a potential vulnerability where socket creation failures (due to invalid address family parameters, system resource constraints, or other socket-related issues) could result in unhandled exceptions.

The function is used by the port management system to determine which address families (IPv4/IPv6) are available for binding. This change ensures that the port handling logic in handle_port remains stable even when socket creation fails, as the function will now properly return False instead of crashing with an unhandled exception.

The modification maintains the same error handling behavior and return values while providing comprehensive exception coverage for all socket-related operations. This follows defensive programming principles by catching exceptions as early as possible where they can be meaningfully handled.

Confidence score: 5/5

• This is a very safe defensive programming improvement with no risk of breaking existing functionality
• The change only adds exception protection without altering the function's behavior or return values
• No files need additional attention as this is a contained, well-scoped improvement

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}