Fix incorrect port availability check in get_free_port

[mohityadav8]

🐞 Fix for Issue #503
Close #503

Problem

The function get_free_port in challenge/utility.py incorrectly checks port availability using:

if result != 1:

However, socket.connect_ex() returns:

• 0 when the connection succeeds (port is in use)
• non-zero when the connection fails (port is available)

This incorrect condition can lead to incorrect detection of free ports.

Solution

Updated the condition to:

if result != 0:

This correctly identifies ports that are not currently in use and available for binding.

Changes

• Updated port availability check in challenge/utility.py
• Ensures get_free_port returns a truly free port

Testing

• Verified that the function now correctly returns an available port within the specified range.