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

[WIP] fall back to -no-client behavior if client CLI fails to launch #26

Closed
wants to merge 1 commit into from

Conversation

afeld
Copy link
Contributor

@afeld afeld commented Jan 7, 2017

Closes #19.

This is simpler and more comprehensive than checking for the existence of each of the values we pass through, and should catch all of the same errors (though not with the same granularity).

Trying to figure out how best to test this. @jmcarp @jcscottiii Thoughts?

This is simpler and more comprehensive than checking for the existence
of each of the values we pass through, and should catch all of the same
errors (though not with the same granularity).
@jcscottiii
Copy link
Contributor

jcscottiii commented Jan 9, 2017

hmm. my question is that fallback desired behavior? (the answer could be yes, i'm just asking)

typically when you provide arguments, you want it to do that. so by it going back to --no-client, it might be weird UX.

code-wise: it LGTM though.

@afeld
Copy link
Contributor Author

afeld commented Jan 10, 2017

is that fallback desired behavior?

That's a good question. I suppose it could say "Couldn't connect. Run with -no-client if you'd like to connect your client manually." Preference?

/cc @jmcarp @yozlet for input

@yozlet
Copy link

yozlet commented Jan 10, 2017

I don't have a major opinion on this, but @jcscottiii 's point rings true for me. The fact that there's now a separate --no-client behavior implies that we don't want it to act that way if we exclude that flag. So yes, I get the feeling it should quit with that message, but I could be persuaded otherwise.

@markdboyd markdboyd changed the base branch from master to main April 17, 2023 13:33
@markdboyd markdboyd closed this Jul 13, 2023
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.

Handle unknown broker/service key structures
4 participants