slack

Description:

Permission

In the screenshot below (from a CZO message), the pencil icon is incorrectly placed on its own line. Instead, it should be at the end of the title line. This may be related to having a multi-line title, but I have not tested this hypothesis.

![Screen Shot 2022-01-11 at 2 56 30 PM](h

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.

The README has links that don't work when viewed from PyPi. An example, which uses /tutorial as a relative path, resulting in a 404. The Table of Content anchors also appear to not work as intended.

Links on the project page should be reviewed and updated to

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

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.

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

I am attempting to parse an array.

{
  "servers": [
    {
      "servername": "server1",
      "serveractiveconn": 0,
      "servertotalconn": 20,
      "serverconnections": [],
      "serverssl": 1,
      "serversslinfo": "",
      "serveractive": true,
      "servererror": "",
      "serverpriority": 0,
      "serveroptional": 0,
      "serverbps": "0 "
    },
    {
 

There is no reason not to use an env variable for the stateSecret:

The sample code in the docs for Bolt Oauth setup has the stateSecret exmple in single quotes as text, whereas for the client id or client secret it puts it as an env variable. Is there a reason that the stateSecret isn't an env variable? Is the stateSecret supposed to be generated randomly each time the app install process is