Skip to content
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.

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

Let the OS choose the server port when the config doesn't have one. #504

Merged
merged 2 commits into from
Nov 3, 2015

Conversation

hernando
Copy link

Among other things, this is needed to be able to run tests that use
config files in parallel reliably.

@eile eile self-assigned this Oct 23, 2015
@@ -578,7 +578,7 @@ serverConnection: EQTOKEN_CONNECTION
'{' {
connectionDescription = new eq::server::ConnectionDescription;
connectionDescription->setHostname( "" );
connectionDescription->port = EQ_DEFAULT_PORT;
connectionDescription->port = 0; // OS chosen port
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ui, so innocently looking, but still a dragon. This at least should break the admin API for window creation. Investigating.

@eile
Copy link
Member

eile commented Oct 23, 2015

convert11Visitor.h:49

@hernando
Copy link
Author

Shouldn't convert11Visitor.h:49 be also 0 and remove EQ_DEFAULT_PORT completely?

@eile
Copy link
Member

eile commented Oct 23, 2015

Yes, was more a note-to-self.

@hernando
Copy link
Author

With this commit RTNeuron can create auxiliary windows for the offscreen snapshot.

@eile
Copy link
Member

eile commented Oct 26, 2015

+1 if convert11Visitor.h:49 is using '0'

@hernando
Copy link
Author

I've removed the spurious warning from Client::connectServer.

if( server->getConnectionDescriptions().empty( ))
{
connDesc = new co::ConnectionDescription;
connDesc->port = EQ_DEFAULT_PORT;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, this should stay. This is for the standalone server, which still runs on the hardcoded port.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed it without remembering there was a tool to start a server process.
I've never used the resident server process and I don't think I'll ever use it. For debugging purposes I've always found misleading to have a connection error trying to access the default server (where default means a different port in each machine because the uid may change, so it's not really hardcoded). Since having a resident server is not the primary use case, don't you think it's better to require the server URI explicitly in this case with EQ_SERVER (explicit better than implicit).

This was already the case when no configuration file was provided,
the behavior is now extended to the configuration files where the port
is not given.
This is needed to be able to run tests that use config files in parallel
reliably.
@hernando
Copy link
Author

Failing because the GPFS is down in Lugano.

@eile
Copy link
Member

eile commented Oct 27, 2015

+1

@hernando
Copy link
Author

retest this please

eile added a commit that referenced this pull request Nov 3, 2015
Let the OS choose the server port when the config doesn't have one.
@eile eile merged commit 30c6a69 into Eyescale:master Nov 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants