slack-ruby / slack-ruby/slack-ruby-client
Reasonable Timeout Limit
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 1.3k
- Forks
- 222
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 3
Description
Hello Slack Team,
I'm not sure if this is the right forum for this question, but for users of this gem, is there a recommended setting for timeout?
I have an internal app that sends messages to my workspace via chat_postMessage when certain internal events happen (sending a dozen of messages per minute). My current open and read timeouts are both set at 3 seconds. Everyday, I see a handful of Faraday::ConnectionFailed being thrown, which then resolves themselves upon retry. Is 3 second a reasonable timeout? Please feel free to point me to any official doc or share some recommendations/best practices around this.
Thank you very much for your time and attention!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by reviewing the gem's timeout configuration and the official Slack and Faraday guidance referenced by the question. The work is complete only when a specific timeout recommendation or documented best practice is established, which this issue does not currently define.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100