Christian Muehlhaeuser

@ahmetb: The channel should now be closed if an error occurred. We still need to propagate the error properly, but at least you shouldn't end up with a dead-lock any...

@ChimeraCoder: LGTM! @jrdnull: Would you mind rebasing / squashing that for us?

@wangxufire: Is this really the sensible thing to do here? Which situation would it improve?

That being said, you are clearly right that this situation should be handled better. I just think the real fix needs better error handling.

#222 should be a fix for this scenario. It lets each TwitterApi maintain its own oauth-client.

@Kimau: Have you ever figured out the cause of your issue?

Didn't work with 2.15, updated to 2.16 just this morning, but no dice.

Thanks! I've tried enabling security credentials for the device now, but it doesn't accept the username/password combination I entered. Guess I have to reset it altogether.

> Also having this issue, but using a NodeMCU CP2102 ESP-12E. What was the solution? Even if I reflash the board, it retains memory of the SSID and password. Never...

We're using cobra for flag handling, but it can just as easily create completions for us. Edit: Scratch this, I'm obviously wrong and we're *not* using cobra for flag handling...