slack

Expanding the compose box (by clicking ^ in the upper right of the compose box) is a relatively new feature, and needs to be documented.

We should add a documentation page titled "Resize the compose box", indexed just below "Open the compose box". It should provide instructions (in separate sections) for how to:

1. Expand the compose box
2. Collapse the compose box
3. Stretch the compose b

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

Describe the bug
The button to toggle the chat widget doesn't have discernible text.

To Reproduce
Steps to reproduce the behavior:

1. Go to a page with the Papercups chat widget installed.
2. Check accessibility with axe DevTools
3. See Buttons must have discernible text issue

Especially for IRC, the outgoing IP address can matter a lot. Need some way to set which one to use on a box that has many.

Is there an existing feature request for this?

• I have searched the existing issues

Describe the Feature

Implement "dbt snapshot --defer", which would behave similar to "dbt run --defer".

Describe alternatives you've considered

No response

Who will this benefit?

When trying to set up "slim ci", one step in my case would be to run snapshots based on other dbt models.

I like love the sidebar horizontal option, but I it would be great if there were an additional option to have the horizontal sidebar at the bottom of the window instead of the top.

Thanks!

Currently, https://slack.dev/python-slack-sdk/socket-mode/index.html has only Events API example. We add interactivity patterns (e.g., shortcuts, modal submission, button clicks, etc.) in the page.

@~tjstum Thanks for your prompt reply here!

I might suggest adding something to the docs of SocketModeRequest (and the example usages) mentioning that the WebhookClient/AsyncWebhookClient ca

We don't have any document pages for "Sign in with Slack" feature while having an example app in the repo: https://github.com/slackapi/node-slack-sdk/tree/main/examples/openid-connect

List any relevant URLs

• https://slack.dev/node-slack-sdk/oauth

Requirements

Please read the Contributing guidelines

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

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.

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:

``

Description

The workflow setup documentation in bolt-js does not describe the need to add workflow step(s) to api.slack.com/apps. Without this part, then workflow steps would not show up in Workflow Builder of a workspace.

Related to #1156.

What type of issue is this? (place an x in one of the [ ])

• documentation related