Carson Ip

+1 ``` bower angular-media-queries#* not-cached https://github.com/jacopotarantino/angular-match-media.git#* bower angular-media-queries#* resolve https://github.com/jacopotarantino/angular-match-media.git#* bower angular-media-queries#* checkout 0.6.0 bower angular-media-queries#* mismatch Version declared in the json (0.5.0) is different than the resolved one (0.6.0)...

This is actually a reasonable request but it may be hard to describe these 3 options on skill startup. I will have to think about how to present these options...

Sounds good. I'll work on it soon.

Could you elaborate a bit about the problem and how to reproduce the problem? That would really help me identify the problematic part.

I don't even know there's a new echo wall clock. My guess is that it will work since this works like a normal Alexa skill. Please let me know if...

Oh no. My bad. Sorry for the misunderstanding. This skill is not a "real" timer. The clock's LED will not have any respond. This skill works with all Echo devices...

This skill was created when Alexa did not have timer related functionalities exposed to developers. I just realized it is now accessible to developers. I will look into this feature...

@lekhajk Do you have your librdkafka's version? Will an upgrade of librdkafka fix this?

The reason I asked this is that I share the client object and producer object throughout the code. Adding reconnect code may add complexity.

My experiment shows that recreating producer on exception will do. But there will be errors like this occasionally after reconnect: ``` Traceback (most recent call last): File "bin/test-kafka.py", line 13,...