Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
the8woodcutter
@thewoodcutter
finally, just needed a bit more perserverance
@nzlosh thanks o7
Sijis Aviles
@sijis
The Admin definition jid should also be able to support wildcard, possibly regex too.
zhongguozhi2
@zhongguozhi2
test
Carlos
@nzlosh
For anyone using errbot with discord, the discord.py framework https://github.com/Rapptz/discord.py that the discord backend depends on, has been put into archive mode and the maintainer has officially stepped down. For the full story, you can see the gist here https://gist.github.com/Rapptz/4a2f62751b9600a31a0d3c78100287f1. Long story short, Discord has made a lot of changes to how external bots can interact with their service which has caused friction between bot library developers. Discord's Slash Commands sound like a game changer that library developers can't/won't support. I'll try to get a better understanding of where slash commands are going and what that will mean for errbot.
asjrosabal
@asjrosabal
Hi everyone. I'm using Errbot in Slack channel, how can I send a csv file to someone? Any idea. Thanks
Sijis Aviles
@sijis
Sijis Aviles
@sijis
Errbot is part of hacktoberfest. Feel free to look at issues and see if theres something that you feel you could tackle. If there isn't thats ok. Other fixes / features are appreciated too.
Ivan
@Nov1kov
Hello. Do you know a way to set specific backend token for each plugin?
Carlos
@nzlosh
@Nov1kov can you elaborate? Errbot doesn't support connecting multiple backends with a single instance
Ivan
@Nov1kov
I need plugins that can send messages from different bots but in the same messenger. it looks like multibackends but in the same messenger... I understand, looks like it not for Errbot
Carlos
@nzlosh
@Nov1kov Errbot plugins are generally developed by end users for their specific needs. There are 3rd party plugins that you can use if they do what you need. Errbot loads plugins on startup but can load/unload them at runtime. Once a plugin is loaded it can send messages to the chat backend that Errbot is connected to (a chat backend could be IRC, XMPP, Slack, Discord, Gitter, etc). It's possible to install the same plugin on multiple Errbot instances which would give the same bot behaviour across all backends.
Ivan
@Nov1kov
@nzlosh thanks!
Carlos
@nzlosh
@Nov1kov You're welcome. I'm not really sure if I answered your question, but if you have any more, feel free to post them here and we'll do our best to help you out.
Jeffrey Jen
@yihungjen_twitter
Hello! On reading bot flow context, is it purely in memory, or does it persists somewhere?
Sijis Aviles
@sijis
I'm pretty sure it persist within the local storage of the plugin.
cryptodog557
@cryptodog557
Hey peeps
Sijis Aviles
@sijis
@cryptodog557 welcome.
Unam LN
@fulljackz
Hi folks, I'm currently discovering errbot with zulip.
Is there a way to lower() a function name, allowing to call @bot test and @bot TeSt the same code ?
alpinweis
@alpinweis
Hi. I'm trying to migrate to the SlackV3 backend. How do I call slack API methods now?
It used to be self._bot.api_call(method, data={}). Now any method I try to call complains something like api_call() got an unexpected keyword argument '<somename>'.
Say, I need to call conversations.create with a POST payload.
alpinweis
@alpinweis
I guess I could use self._bot.slack_web directly instead of self._bot.api_call, e.g. self._bot.slack_web.conversations_create(name="test").
Is this the correct way to do it or is there a better/recommended way?
Carlos
@nzlosh
@alpinweis can you open an issue please and I'll take a look
alpinweis
@alpinweis
Thanks @nzlosh. Just opened errbotio/err-backend-slackv3#54
Carlos
@nzlosh
:thumbsup: @alpinweis thanks for that. Having a github issue gets more visibility around the problem and any potential workaround/fix.
alpinweis
@alpinweis
@nzlosh are there plans to tag err-backend-slackv3 releases? when setting up the backend (via git clone err-backend-slackv3) it might help having a more stable version instead of the master head
Carlos
@nzlosh
That'd be a good idea now that it is in its own repository.
@sijis do you have any opinions on how releases for backends should be managed/defined as part of the larger errbot project?
Sijis Aviles
@sijis
@nzlosh I think they should be independent. They don't have to match the release version of the main project. If there are breaking changes, then some coordination may need to occur but that's far and few right now
Tagging a release sounds like a great idea
Hoping to cut a release early December. I'm considering adding a deprecation notice, in that release, to the built-in slack backends and point folks to v3 as part of message.
Carlos
@nzlosh
Sounds good. The more people we having using slackv3, the more edge cases we'll catch and fix. I saw that the @ mention fix has in the markdown module has been released, so I'll update the requirements file and tag this change as v0.1.0 as a starting point for versioning.
Sijis Aviles
@sijis
Sounds good
Carlos
@nzlosh
OK, v0.1.0 for the slackv3 backend has been released.
Carlos
@nzlosh
@Vaelor The mattermost backend release is currently on v2.0.2 27 Nov 2017. Would you be OK with creating a new release v3.0.0 for the current HEAD on the master branch?
Carlos
@nzlosh
@Vaelor I've opened a PR to create a v2.1.0 release since there aren't any major breaking changes between 2.0.2 so version 3.0.0. wasn't justified. errbotio/errbot-backend-mattermost#52
Carlos
@nzlosh
@sijis should backend maintainers have contributor rights to https://github.com/errbotio/err-backend-gitter? I don't seem to have the ability to create a release for this repo.
Sijis Aviles
@sijis
There should. I can check later tonight and verify
Carlos
@nzlosh
The mattermost backend v2.1.0 has been officially released. https://github.com/errbotio/errbot-backend-mattermost/releases
Sijis Aviles
@sijis
found this article interesting, how chatbot can improve dev/ops workflow (in this case, oncall) https://github.blog/2021-12-01-using-chatops-to-help-actions-on-call-engineers/
alpinweis
@alpinweis
Hi.
I have a message that I need to send to a given Slack channel and pin it to that channel.
Given a slackV3 backend, is there an easy way to do that? So, basically, to add a pin, I need to get the timestamp of the latest message that I sent using something like:
self.send(self.build_identifier(MYCHANNEL), "some text to pin") ?
Carlos
@nzlosh
I don't konw of an easy way that exists to get the timestamp for a message that was sent. I took a quick look but can't see anywhere in errbot's code where a timestamp is created for when a message was sent. If there was such a thing, there'd be no guarantee that errbot's sent timestamp would match Slack's message timestamp so it probably be useless for this case even if it did exist. The bot does see the messages it posts. The message handling code ignores messages from the bot, but perhaps there's a way to get access to the message from the plugin to extract the timestamp?
Sijis Aviles
@sijis
I thought there was a flag that could toggle if the bot ignores itself or not.
alpinweis
@alpinweis
Currently errbot's methods send (in core) and send_message do not seem to return anything, as opposed to, say, slack client's chat_postMessage method.
The latter returns a blob with the posted message's timestamp which is used to pin it. It'd probably make sense for errbot's send/send_message to return something similar. That would make it easy to pin the latest sent message.
Carlos
@nzlosh
I think those functions aren't expected to return anything so that backends can be designed to run synchronously or asynchrously. Your comments got me thinking and there is a callback method that you might be able to use https://errbot.readthedocs.io/en/latest/user_guide/plugin_development/messaging.html#trigger-a-callback-with-every-message-received to get at the message information.
alpinweis
@alpinweis

My bot (slackV3) creates new slack channels. I have a command to rename a channel.

 !channel mv #old-name #new_name

Just noticed if #old_name is passed as an identified slack channel (like when it gets picked from a drop down menu) - the command does not seem to reach the bot and is kind of ignored.
Not sure why. Is this expected?

Carlos
@nzlosh
That should work. Could you create an issue with any debug logs that were created when the command was executed please?
I noticed that slack transforms the channel name into this thing here <#CL8HNNTFY|errbot-dev-test> (errbot-dev-test is the channel name). I'm a little suspicious that markdown processing may be attempting to process it as html content. The slackv3 backend has already been bitten my slacks @ mention format being incorrectly processed by the markdown module.
If it's not markdown having trouble, then my next guess would be the identity parsing code in errbot.