Chunyang Wen

Is it necessary that creating a separate `Spec` for ElasticDL? > The short answer is yes. First let's review the example in ElasticDL's model zoo we mentioned during last meeting:...

@workingloong Any update on this issue? If not, I can try to fix the problem.

After a further investigation into the code base, it seems that the `err_msg`'s length is used to indicate the status of a mini-batch. If any worker reports a non-empty message...


In opsdroid/connector/slack/events.py `response_type` is hard coded into `in_channel`. https://api.slack.com/interactivity/slash-commands There is a message visibility: - ephemeral - in_channel The previous one is what I needed.

Yep. That PR is not merged then

Double check the PR. It is a configuration for the connector. I agree with @FabioRosado in #1957 that it is better we support both cases - A connector level configuration...

It seems that Travis break(caused by van.cc) has nothing to do with this PR.

Maybe users have set a large history size? And a lot of images copied.(Just random guess)

I think this may be a little too hard. Because multiple functions relay on number, such as key range. One of the change should be specialized the template of converting...