-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slack Command !search #72
Comments
Hello, I would like to work on this |
I would like to take this task. |
Hey, I would like to try and resolve this issue, by adding the !search command. Request you to assign it to me. |
@harjyotbagga We'd love the help. If you have any questions, let us know! |
Thanks for the positive response! 😄 I've started working on it. Please assign this issue to me. I'll get back in a couple of days. |
@aaron-suarez I needed a bit of help.
After which I tried running the command on slack, giving me a "dispatch error" and "401 Unauthorized" on my terminal. Pl note, I have verified the auth tokens and there is no issue there. I would appreciate some guidance from your end. [https://github.com/slackapi/bolt-js/issues/579 ] A similar issue has been reported here. |
Oh weird, so the bot itself is producing a 401? What happens when you hit it manually (with like Postman or curl, rather than going through slack)? |
I have tried sending the request via Postman. I made an OAuth2.0 authentication token by reading the Slack App docs and sent a POST request to https://df94f7be0da7.ngrok.io/slack/commands?command=roll after I updated the slash command request URL in the slack app dashboard. |
If you join our slack team at https://operationcode.org/join I'd be happy to set up a slack call and pair with you on troubleshooting it. I don't know from just looking at it what the problem could be. |
I just got the |
Note, it does not happen on prod right now (which is good). I wonder if it's something that we introduced recently... |
I think it might be related to #227. @LivingInSyn did you ever see this |
Little chance it was this change. All I did was change a n+1 to n
…On Fri, Oct 9, 2020 at 6:26 PM Aaron Suarez ***@***.***> wrote:
I think it might be related to #227
<#227>.
@LivingInSyn <https://github.com/LivingInSyn> did you ever see this
"dispatch_failed" situation when you were working on the issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#72 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQMJCLBK7UET2FAZN6SNWLSJ6E2NANCNFSM4HK4MAEA>
.
|
I noticed that we merged that to master directly and our branches are based on staging, so it's true, it's not due to #227... Perhaps another recent change. I'll dig deeper when I have a chance, I'm not sure I'll be able to right now |
I was able to resolve it by making sure that the right |
We'll be implementing this based on previous work into the new rewritten bot. This one is fairly low priority though so may take a bit. |
!search how to print line java
will look through stackoverflow or google for results and then post a link.The text was updated successfully, but these errors were encountered: