-
Notifications
You must be signed in to change notification settings - Fork 171
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
AttributeError: 'SlackBackend' object has no attribute '_people' #409
Comments
Hey @codingmaths is that the entirety of the log? Could you try restarting Will and capturing everything from bootup to you sending a hello command in a gist and link it here? |
Whoops, didn't mean to close this! |
@rsalmond I have resolved this issue by using rtm_connect instead of rtm_start , I have changed slack client.py and server.py for same. Now I am getting below error when I try to run command on slack `` [DEBUG] https://slack.com:443 "POST /api/rtm.connect HTTP/1.1" 200 281 |
Those files are not familiar to me. Do you mean you modified the slack client itself?
It seems like there may be a case where this can occur if the client has not yet connected to the server. If possible could you capture the complete Will log from startup time till the exception occurs and paste it into a gist and share the link here? |
what should be the config.py configuration for slack backend. I am using :
do we need to add user details as well, in config.py |
Hey @codingmaths thanks for the gist that helps. It looks like both the error you see there and the exception you posted earlier are related to the Slack IO adapter having not updated the If you want to fork Will to work on it we would be happy to help review your code, but trying to triage an issue on a modified Will using a modified Slack client without source is going to be extremely difficult. If you can document the issue using the stock Slack client and the latest stable release of Will then we can try to replicate the issue and work with you to fix it. As far as the user details go you should be able to configure those in the Slack UI. |
@rsalmond . I think rtm.connect won't work with willbot , since bot also need channel details while connecting with slack. but with rta.connect we don't get that detail. please refer slack_rtm . Now I have removed all the code changes which I have done and using default config. also using rtm.start to connect slack workspace. here is my observation: I am getting none response after authenticating with my slack workspace. with my experience I am able to authenticate app with slack but after that I am not getting any response from slack app. Instead I am getting none. Please refer below log for same: DEBUG errbot.bootstrap Start serving commands from the slack backend. 23:22:13 DEBUG errbot.backends.slack Token accepted 23:22:13 INFO errbot.backends.slack Connecting to Slack real-time-messaging API 23:22:48 DEBUG root RTM connected let me know , if you need further details. |
Closing out as we'll be using the events api per #428 |
I am able to connect will with our slack channel, but when I try to chat from my slack channel, I am not getting any response from Will.
** Log **
[DEBUG] https://slack.com:443 "POST /api/rtm.start HTTP/1.1" 200 None
** Will plugin for bonjour **
from will.plugin import WillPlugin
from will.decorators import respond_to, periodic, hear, randomly, route, rendered_template, require_settings
class BonjourPlugin(WillPlugin):
** Slack command **
@lazypanda bonjour
WILL_HANDLE = "lazypanda"
our slack workspace have more than 20K users, not sure if that is the issue.
The text was updated successfully, but these errors were encountered: