Slack Command !search

[operationcode]

Slack Command !search

[harjyotbagga]

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.

[the-bose]

Hello, I would like to work on this

[utkryuk]

I would like to take this task.

[harjyotbagga]

Hey, I would like to try and resolve this issue, by adding the !search command. Request you to assign it to me.
Since I'm just starting out with open source, it'd be great if you could give me a week's time, to solve this issue with a PR. 😄

[aaron-junot]

@harjyotbagga We'd love the help. If you have any questions, let us know!

[harjyotbagga]

@aaron-suarez I needed a bit of help.
I followed all the steps in the readme.

• Made a slack app and integrated it into my workspace.
• Updated the pybot.env variables, using the Secret code and the O-Auth token from the Slack app.
• Installed all dependencies and was able to successfully run the bot on the localhost.
• Made my localhost open to the public using ngrok.
• To test a few commands, I added the command in slash-commands on the slack API, setting the URL as https://54bac023ae26.ngrok.io.

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.

[aaron-junot]

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)?

[harjyotbagga]

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.
I got a 500 Server Internal Error that looks something like,

I am not able to understand how do I fix this internal error. I am getting no error on the python terminal when I send the command via slack, but the response states /roll failed with the error "dispatch_failed" and the the ngrok terminal still says 401 Unauthorized.
Any guidance would be more than helpful.

[aaron-junot]

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.

[aaron-junot]

I just got the /roll failed with the error "dispatch_failed" error on my slack workspace as well... I'm wondering if this warrants an issue. @AllenAnthes when you get a chance can you check and see if you also get this error?

[aaron-junot]

Note, it does not happen on prod right now (which is good). I wonder if it's something that we introduced recently...

[aaron-junot]

I think it might be related to #227. @LivingInSyn did you ever see this "dispatch_failed" situation when you were working on the issue?

[LivingInSyn]

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> .

[aaron-junot]

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

[aaron-junot]

I was able to resolve it by making sure that the right ngrok url was in, and that my bot was running correctly. So I'm thinking it might be an issue like that @harjyotbagga

[JudsonStevens]

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.