Port number 65535 is valid for using #256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

dmitry-lipetsk opened this issue May 7, 2025 · 0 comments · May be fixed by #255

Assignees

Labels

Collaborator

dmitry-lipetsk commented May 7, 2025 •

edited

Loading

Testgres cannot allocate a port number 65535, because it uses the range(1024, 65535):

testgres/testgres/impl/port_manager__generic.py

Line 23 in edd64db

self._available_ports: typing.Set[int] = set(range(1024, 65535))

I think we have to allow usage of 65535 port number to enlarge our valid range of ports )

The fix is trivial - set ( range ( 1024 , 65536 )

Another problems in this code will be fixed, too.

See also

https://www.ncftp.com/ncftpd/doc/misc/ephemeral_ports.html

The text was updated successfully, but these errors were encountered:

dmitry-lipetsk self-assigned this

dmitry-lipetsk added a commit to dmitry-lipetsk/testgres that referenced this issue


          [postgrespro#256] A used port range is [1024 ... 65535]

f085b70

PortManager__Generic is updated.

dmitry-lipetsk linked a pull request

that will close this issue

[#247] PortManager__Generic uses lock-dirs for reserved ports #255

Open

dmitry-lipetsk added the enhancement label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment