Skip to content

✨ Quality: Port 0 treated as falsy in getValidPort validation - #8501

Open
lukebaze wants to merge 1 commit into
DevExpress:masterfrom
lukebaze:contribai/improve/quality/port-0-treated-as-falsy-in-getvalidport-
Open

lukebaze wants to merge 1 commit into
DevExpress:masterfrom
lukebaze:contribai/improve/quality/port-0-treated-as-falsy-in-getvalidport-

Conversation

@lukebaze

Copy link
Copy Markdown

✨ Code Quality

Problem

The condition if (port) treats port 0 as falsy, causing it to bypass port validation and call getFreePort() instead. Port 0 is a valid network port (meaning 'any available port'), but this logic incorrectly treats it as 'no port specified'. Users explicitly configuring port 0 will get unexpected behavior.

Severity: medium
File: src/configuration/utils.ts

Solution

Change condition to if (port !== undefined && port !== null) or if (typeof port === 'number' && port > 0) depending on intended behavior for port 0.

Changes

  • src/configuration/utils.ts (modified)

Purpose

Describe the problem you want to address or the feature you want to implement.

Approach

Describe how your changes address the issue or implement the desired functionality in as much detail as possible.

References

Provide a link to the existing issue(s), if any.

Pre-Merge TODO

  • Write tests for your proposed changes
  • Make sure that existing tests do not fail

🤖 About this PR

This pull request was generated by ContribAI, an AI agent
that helps improve open source projects. The change was:

  1. Discovered by automated code analysis
  2. Generated by AI with context-aware code generation
  3. Self-reviewed by AI quality checks

If you have questions or feedback about this PR, please comment below.
We appreciate your time reviewing this contribution!

Closes #8500

…dation

The condition `if (port)` treats port 0 as falsy, causing it to bypass port validation and call getFreePort() instead. Port 0 is a valid network port (meaning 'any available port'), but this logic incorrectly treats it as 'no port specified'. Users explicitly configuring port 0 will get unexpected behavior.

Affected files: utils.ts

Signed-off-by: 0xKermini <67284748+lukebaze@users.noreply.github.com>
@testcafe-need-response-bot testcafe-need-response-bot Bot added the STATE: Need response An issue that requires a response or attention from the team. label Mar 26, 2026
@aleks-pro aleks-pro removed the STATE: Need response An issue that requires a response or attention from the team. label Mar 31, 2026
@github-actions

Copy link
Copy Markdown

This pull request has been automatically marked as stale because it has not had any activity for a long period. It will be closed and archived if no further activity occurs. However, we may return to this pull request in the future. If it is still relevant or you have any additional information regarding it, please leave a comment and we will keep it open.

@github-actions github-actions Bot added the STATE: Stale An outdated issue that will be automatically closed by the Stale bot. label Sep 28, 2026

This branch had an error being deployed

1 failed deployment
authentication — 6df86fa9 Deployed Mar 26, 2026 by lukebaze via authenticate #4914
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

STATE: Stale An outdated issue that will be automatically closed by the Stale bot.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(configuration): port 0 treated as falsy in getvalidport validation

2 participants