You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking for help on an issue I'm having while using this gem. Is there a natural way to respond to Slack immediately upon receiving an event with a 200 status? I've been having the issue that if any of the code in my commands takes too long to complete, Slack resends the event, causing our bot to occasionally post to a channel 2-3 times. It seems like currently a success status isn't returned to Slack until the self.call method reaches its end. This has also been a pain when debugging, as throwing a binding.pry in a command to troubleshoot something has the pry reopen every time Slack resends the event.
The text was updated successfully, but these errors were encountered:
There's no built-in way today in Grape to return a 200 status, and keep processing the request afterwards. This is something that I would like to have implemented, potentially built into slack-ruby-bot-server-events.
I would try to defer execution within the callback, which could be done with async, as discussed in slack-ruby/slack-ruby-client#237 and socketry/async-websocket#2. If you can make it work, maybe we can discuss how to make it available as an extension for others to reuse?
Looking for help on an issue I'm having while using this gem. Is there a natural way to respond to Slack immediately upon receiving an event with a 200 status? I've been having the issue that if any of the code in my commands takes too long to complete, Slack resends the event, causing our bot to occasionally post to a channel 2-3 times. It seems like currently a success status isn't returned to Slack until the
self.call
method reaches its end. This has also been a pain when debugging, as throwing a binding.pry in a command to troubleshoot something has the pry reopen every time Slack resends the event.The text was updated successfully, but these errors were encountered: