slack

This issue is about the Settings > Organization permissions > Message editing > "Allow message editing" drop-down option.

At present, this dropdown has a choice labeled "Up to N minutes after posting". Using a variable in the user-facing description of the option can be confusing and off-putting to users.

Instead, we should label this option as "Custom", similarly to the option in the "Waiti

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.

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!

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Running dbt deps in a nightly job failed after retrying downloading the packages. The Max retries is listed as 5 and was currently at 0.

Expected Behavior

The download is retried until the max retries is reached or the package is downloaded successfully.

Steps To Repro

Reproducible in:

The Slack SDK version

All versions

Steps to reproduce:

from slack_sdk.models.blocks import DividerBlock
DividerBlock() == DividerBlock()

It happens with any pair of equivalent blocks.

Expected result:

True

Actual result:

False

Suggested solution

Implementing __eq__ in JsonObject.

class Json

Description

When faced with updates from one version to the next it’s important to look at the changes between the version and as I see you are treating this with the proper care.

However, the Github UI does not help here a lot to understand the changes for one package like @slack/web-api as there are 7 other package changelogs mixed up with the change for the package you currently car

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