[jira] [Work logged] (CURATOR-535) TestServer random port selection has a race condition

[ https://issues.apache.org/jira/browse/CURATOR-535?focusedWorklogId=780962&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-780962 ] ASF GitHub Bot logged work on CURATOR-535: -- Author: ASF GitHub Bot

[GitHub] [curator] kezhuw commented on pull request #421: CURATOR-535: Fix client port conflict due to untrustworthy random port allocation

kezhuw commented on PR #421: URL: https://github.com/apache/curator/pull/421#issuecomment-1154615488 Ideally, it should be possible to bootstrap `TestingCluster`(with unspecified ports) too with help from `reconfig`. But there are difficulties since election port, quorum port were not desig

[jira] [Work logged] (CURATOR-535) TestServer random port selection has a race condition

[ https://issues.apache.org/jira/browse/CURATOR-535?focusedWorklogId=780960&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-780960 ] ASF GitHub Bot logged work on CURATOR-535: -- Author: ASF GitHub Bot

[GitHub] [curator] kezhuw opened a new pull request, #421: CURATOR-535: Fix client port conflict due to untrustworthy random port allocation

kezhuw opened a new pull request, #421: URL: https://github.com/apache/curator/pull/421 This commit try to solve port conflict for unspecified port: * Set port after `bind(0)`. * Compat old behaviors by postponing random port allocation to `getPort`. It is encouraged to `getPort`