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

[TIMOB-26462] Improve error handling and logging when failing to connect to log server #10384

Merged
merged 2 commits into from Oct 18, 2018

Conversation

ewanharris
Copy link
Collaborator

JIRA: https://jira.appcelerator.org/browse/TIMOB-26462

Totally unsure of the verbiage, any comments on it are more than welcome.

Test steps

  1. Edit your /etc/hosts file to remote the localhost mapping
  2. Build for iOS
    • Build should error informing you that we could not resolve localhost, not that another process is using the port

} else {
_t.logger.error(__('Another process is currently bound to port %d', _t.tiLogServerPort));
_t.logger.error(__('Set a unique <log-server-port> between 1024 and 65535 in the <ios> section of the tiapp.xml') + '\n');
process.exit(1);
Copy link
Contributor

Choose a reason for hiding this comment

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

No need to duplicate process.exit(1). A single call outside the if block would suffice.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Updated

@cb1kenobi
Copy link
Contributor

APPROVED

@build
Copy link
Contributor

build commented Oct 18, 2018

Messages
📖

💾 Here's the generated SDK zipfile.

Generated by 🚫 dangerJS

@sgtcoolguy sgtcoolguy merged commit 86ed0be into tidev:master Oct 18, 2018
@sgtcoolguy sgtcoolguy added this to the 7.5.0 milestone Oct 18, 2018
@ewanharris ewanharris deleted the TIMOB-26462 branch November 13, 2018 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants