Daniel (dB.) Doubrovkine

This is consistent with the behavior observed with faye-websocket. We try to open a lot of connections, and the client can't process them fast enough, causing these `close` events, a...

Hmmm... check out https://github.com/celluloid/celluloid-io/issues/176 and https://github.com/dblock/slack-ruby-client/issues/90, does this explain any of this?

Yes, that sounds just right! Maybe it should be a whole other range of exceptions, would appreciate some research too in other network conditions. Would love a PR!

I think another one is `Errno:EPIPE` and `Errno::ECONNRESET`: ``` E, [2016-06-07T19:05:15.066577 #154] ERROR -- : Actor crashed! Errno::EPIPE: Broken pipe /app/vendor/ruby-2.2.4/lib/ruby/2.2.0/openssl/buffering.rb:383:in `syswrite_nonblock' /app/vendor/ruby-2.2.4/lib/ruby/2.2.0/openssl/buffering.rb:383:in `write_nonblock' /app/vendor/bundle/ruby/2.2.0/gems/celluloid-io-0.17.3/lib/celluloid/io/stream.rb:62:in `block in syswrite' /app/vendor/bundle/ruby/2.2.0/gems/celluloid-io-0.17.3/lib/celluloid/io/stream.rb:390:in `synchronize'...

For easy repro cases, https://gist.github.com/dblock/1250a5497ff3c7af81c05964c459ff86.

Closed the wrong issue, reopening ;)

This library deliberately raises exceptions for _all_ errors by design, so you don't have to be checking the nagging `ok` field in responses which litters everyone's code. This is implemented...

I think Block Kit is its own thing, since it doesn't depend on the Slack API in any way. So I vote for a separate project. I would call it...

I can just make a repo for you and make you admin. Before I do that, have you seen https://github.com/CGA1123/slack_block_kit-ruby?

> Does slack-ruby-client not support all the [chat.postMessage](https://api.slack.com/methods/chat.postMessage)? I am trying to create a block message but I can't seem to send username with `chat_postMessage` It supports all, including [username](https://github.com/slack-ruby/slack-ruby-client/blob/master/lib/slack/web/api/endpoints/chat.rb#L174).