by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Dustin S
@texnofobix
Submitted errbotio/errbot#1427 with workaround/possible fix.
Chris T
@cthom
Is there a way to automatically install specific plugins when errbot starts up? I have a custom plugin in a repo, and I can use the !repos install command manually, but I would rather just insert some code to do that automatically each time.
Sijis Aviles
@sijis
@cthom if you put the plugin inside the plugins directory before the bot is started, it should autoload.
shivakumar-anandan
@shivakumar-anandan
@sijis i'm trying out the new beta SlackRTM backend.
slack.errors.SlackApiError: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'not_allowed_token_type'}
got the above error :-|
`BOT_IDENTITY = {
'token': 'xoxb-'
}'
shivakumar-anandan
@shivakumar-anandan
any pointers to debug would be of great help.. thx.. going through the code.. will let you if i get any resolution..
thx man
Chris T
@cthom
@sijis -- yep, I have done that in the past. I recently moved it into a separate git repo so that I can reload it when I make changes. I am deploying via a docker container hosted in kubernetes, so if i include the plugin in the build, every change needs a container rebuild/redeploy. I'll go that path if needed, but would prefer another way, if possible.
Mark Sullivan
@marksull
@cthom Your BOT_DATA_DIR and BOT_EXTRA_PLUGIN_DIR should point to a docker persistent volume so that they are outside your container. So whenever you redeploy your container you plugins and data will still be present.
Chris T
@cthom
@marksull -- brilliant! I hadn't thought of that, but that's a simple solution. Thanks :)
dgf012
@dgf012
ff
caoyouming
@caoyouming
hello
what`s that?
Alex Sheluchin
@sheluchin
Is anyone at all able to make sense of what Slack is doing with their API? Classic Apps, Legacy Apps, Web API, Events API, RTM API, token deprecation, block builder, Slack Apps... some pending deprecation, some not... then there is the Python slackclient which is building lots of RTM support lately (https://github.com/slackapi/python-slackclient/blob/master/docs-src/changelog.rst), although RTM looks like it's being deprecated as well https://github.com/slack-go/slack/issues/654#issuecomment-578976452
Sijis Aviles
@sijis
I don't think you are alone. I've been confused too
Ken Faria
@kfaria
@sijis Was just a little confused with the nomenclature with the introduction of the SlackRTM Backend. Is errbot going to eventually stop using the Web API and rely solely on the RTM Api, or was 6.1.3 just introducing the RTM API to errbot?
Sijis Aviles
@sijis
there's a (beta) backend using the RTM API for slack (which uses a mix of RTM and Webclient). The existing is using the original rtm api provided by slack (and the python-slackclient)
we are essentially trying to do this: https://github.com/slackapi/python-slackclient/wiki/Migrating-to-2.x. and make the new rtm backend same as the current one
Ken Faria
@kfaria
Ahh okay, thanks! Yeah, also trying to understand what Slack is doing with the RTM API moving forward. The migration link does indicate that Slack wants to introduce the Events API in the official SDK, but no mention of whats happening with RTM.
Alex Sheluchin
@sheluchin
@sijis thanks
Sijis Aviles
@sijis
Ya. its a little nuts. The stuff i read the other day mentions that EventsAPI is the way forward and the discussion @sheluchin sent seems to say something similar. I haven't looked at the EventsAPI at all, but based on the discussion, its expecting the app to receive webhook events. As mentioned, no always possible with every organization
alpinweis
@alpinweis
Hi, I'm using err (case-insensitive) as a bot prefix. I noticed errbot reacts to messages starting with error, e.g. when someone types errors can be avoided by bla-bla...
is there a way to prevent this? I need the space separator, but the doc says There's no need to add spaces to the BOT_ALT_PREFIX_SEPARATORS
Carlos
@nzlosh
@alpinweis From a quick look at the code https://github.com/errbotio/errbot/blob/07db5cb741f798a02b1872f90f1e5945a2b294dc/errbot/core.py#L235, even adding a space in BOT_ALT_PREFIX_SEPARATORS wouldn't solve the problem. The issue seems to be that the bot_alt_prefix uses Python's startswith method to match the alternative prefix, then removes the number characters that the separator has. I haven't confirmed this but you might want to enable debugging and look in the logs for the text Called with alternate prefix. The log will show you what the bot has done with the text after processing the alternative prefix.
alpinweis
@alpinweis
Thanks @nzlosh
What's the right erbotic way to send a long string of text as a snippet to slack? There is send_stream_request method, but it's supposed to work with files.
Carlos
@nzlosh
@alpinweis where is the long string of text coming from? If it's being generated internal in a plugin, then calling send_stream_request inside that function seems reasonable to me.
alpinweis
@alpinweis
it's a string generated by the plugin internally, in memory, but the stream method expects a file. I can go with a temp file, but wondering if there is a more elegant way
Carlos
@nzlosh
You might be able to use io.StringIO to pass the string as a stream without writing a temp file to disk.
raspbeguy
@raspbeguy
Hello, I'm trying to connect errbot to my prosody server. I have a problem at the TLS step
21:13:50 DEBUG    sleekxmpp.xmlstream.xmlst Event triggered: ssl_cert
21:13:50 ERROR    sleekxmpp.xmlstream.xmlst Connection error.
21:13:50 ERROR    sleekxmpp.basexmpp        <TagSet object, tags 0:32:16> not in asn1Spec: <OctetString schema object, tagSet <TagSet object, tags 0:0:4>, encoding iso-8859-1>
Traceback (most recent call last):
  File "/opt/bot/venv/lib/python3.7/site-packages/sleekxmpp/xmlstream/xmlstream.py", line 1492, in _process
    if not self.__read_xml():
  File "/opt/bot/venv/lib/python3.7/site-packages/sleekxmpp/xmlstream/xmlstream.py", line 1564, in __read_xml
    self.__spawn_event(xml)
  File "/opt/bot/venv/lib/python3.7/site-packages/sleekxmpp/xmlstream/xmlstream.py", line 1632, in __spawn_event
    handler.prerun(stanza_copy)
  File "/opt/bot/venv/lib/python3.7/site-packages/sleekxmpp/xmlstream/handler/callback.py", line 64, in prerun
    self.run(payload, True)
  File "/opt/bot/venv/lib/python3.7/site-packages/sleekxmpp/xmlstream/handler/callback.py", line 76, in run
    self._pointer(payload)
  File "/opt/bot/venv/lib/python3.7/site-packages/sleekxmpp/features/feature_starttls/starttls.py", line 64, in _handle_starttls_proceed
    if self.xmpp.start_tls():
  File "/opt/bot/venv/lib/python3.7/site-packages/sleekxmpp/xmlstream/xmlstream.py", line 889, in start_tls
    cert.verify(self._expected_server_name, self._der_cert)
  File "/opt/bot/venv/lib/python3.7/site-packages/sleekxmpp/xmlstream/cert.py", line 134, in verify
    cert_names = extract_names(raw_cert)
  File "/opt/bot/venv/lib/python3.7/site-packages/sleekxmpp/xmlstream/cert.py", line 73, in extract_names
    asn1Spec=OctetString())[0]
  File "/opt/bot/venv/lib/python3.7/site-packages/pyasn1/codec/ber/decoder.py", line 1619, in __call__
    '%s not in asn1Spec: %r' % (tagSet, asn1Spec)
pyasn1.error.PyAsn1Error: <TagSet object, tags 0:32:16> not in asn1Spec: <OctetString schema object, tagSet <TagSet object, tags 0:0:4>, encoding iso-8859-1>
I'm on Debian 10
Ken Faria
@kfaria

Hey y'all, and chance of this PR getting merged in? errbotio/errbot#1421

Running into issue where my handle isn't being recognized as a Slack Admin

Tommy Lang
@bopas2

Anyone have any idea why I might be getting this error?

16:11:03 ERROR    slack.rtm.client          When calling '#serve_messages()' in the 'errbot.backends.slack_rtm' module the following error was raised: channelid_to_channelname() missing 1 required positional argument: 'id_'

I'm using the SlackRTM backend. Thanks

Tommy Lang
@bopas2
Ok, using the regular Slack backend fixed this issue, possibly a bug in SlackRTM backend?
Carlos
@nzlosh
Yes, the SlackRTM backend is still in beta stages.
Tommy Lang
@bopas2
Thanks.
Is it possible to use err bot to create slack dialogs? I’m looking into using the slack backend connection directly. As far as I can tell, dialogs require a trigger id which can only be created by using slack slash commands. I think errbot bot commands have the same functionality as a slash command but don’t generate a trigger id. Has anyone tried this before? Thanks!
Tommy Lang
@bopas2
Just checking in to say it is possible to trigger slack dialogs using errbot. Using errbot, you need to send an interactive message that has buttons to Slack. When a user clicks on one of the buttons, slack will then submit a post request to an errbot webhook (if configured correctly on your slack app dashboard). The request will have a payload with a trigger id that can be used to open a dialog. It's a bit roundabout but it is possible.
制杖的龙魂
@G-LongHun
hi
Danoe
@zerophiel
hi
I want to ask how do errbot sending inline keyboard on telegram, is there any documentation about it?
Joanna
@geeitsjo
Hi there team!
Errbott is getting frequent "errbot.backends.slack Cannot find user with ID" error. Has anyone got this problem before?
REQ:
errbot==6.1.2
slackclient==1.3.2
errbot[slack]
Sijis Aviles
@sijis
@bopas2 errbot shod be able to respond to a webhook call it received. It will not be able to generate that multibutton dialog slack though.
If you are looking for a prompt type system., Look at flows https://errbot.readthedocs.io/en/latest/user_guide/flow_development/concepts.html
@zerophiel on the telegram backend. No clue. I work guess it's sending the whole message not individual keystrokes.
@geeitsjo I have personally not seen it but there's a big reported on this. I do believe there is a related or fro the fix, which I have yet to look att.
Stefano Ortolani
@ostefano
Hi, I am trying to understand if ErrBot using the Slack backend is compatible with multiple workspaces deployments. Is that the case?
Carlos
@nzlosh
@ostefano As far as I understand things, you would need an errbot instance per workspace.