Skip to content
#

slack

Here are 5,107 public repositories matching this topic...

nooblag
nooblag commented Oct 27, 2021

It may be desirable in Zulip instances that are invite only for admins/moderators (or any other user with access to core team stream) to be able to track who has been invited, when, and by whom, after a new user has accepted an invite.

Currently, I can see pending invitations that show whom invited whom at Settings -> Organisation -> Invitations but after a user is added, it appears the o

jspeedz
jspeedz commented Sep 5, 2019

What went wrong?

I'm getting deprecation warnings with openSSL encryption.

[2019/09/05 08:38:52][info] Using Encryptor::OpenSSL to encrypt the archive.
[2019/09/05 08:40:22][warn] Pipeline STDERR Messages:
[2019/09/05 08:40:22][warn] (Note: may be interleaved if multiple commands returned error messages)
[2019/09/05 08:40:22][warn]
[2019/09/05 08:40:22][warn] *** WARNING : depre

papercups
dbt-core
jtcohen6
jtcohen6 commented Oct 28, 2021

Folks are used to being able to pass project name as a first positional argument to the dbt init subcommand. The new approach (new for v1!) is much more fun + interactive, but for muscle memory's sake, let's see if we can't find a way to keep supporting dbt init my_new_project, too.

If passed, I think this argument should be used as the implicit answer for "What is the desired project name?

ferdi
mistydemeo
mistydemeo commented Oct 4, 2018

Description

While hubot-slack has support for reconnecting when the connection to Slack is lost, there is a limit to the number of reconnection attempts. If several reconnection attempts fail, the bot will simply hang without a connection. This causes trouble for our process manager, since the client staying open means we don't end up automatically restart it. When this has happened for us

tylerauerbeck
tylerauerbeck commented May 2, 2018

Since adding integration with a number of other external systems, the landing README.md has become a bit cluttered. In addition to that, there's not a lot of detail on some of these integrations (versions,etc.).

What I'd like to do is break up some of the documentation for this and also add some information on what versions of the integrations are supported/tested.

gatus
tiwood
tiwood commented Oct 18, 2021

I've noticed that some of our alerts where failing with the following error message:

Failed to send an serviceAlert for service=Very Cool Service "ServiceYXZ": call to provider alert returned status code 400: Bad payload received by generic incoming webhook.

It seems the issue is caused by unescaped quotes (") in the HTTP POST - in this specific case in the text property:

``

Improve this page

Add a description, image, and links to the slack topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the slack topic, visit your repo's landing page and select "manage topics."

Learn more