Internally raised issue

Describe the bug
If the q process fails to connect to an invalid kafka broker does not throw a q error but prints out kafka errors and returns the client id that would have been used. This is invalid behaviour.

To Reproduce
Run the following in a valid q session initialised with q kfk.q

q).kfk.Consumer[`metadata.broker.list`group.id!`foobar`0]

Expected behavior
Evaluation of the above should error out with an appropriate error indicating that failure was unsuccessful.

Screenshots
There are no relevant screenshots necessary for this

Desktop (please complete the following information):
This issue is os independent and a result of implementation decisions

Additional context
There is no additional context for this issue necessary