slack

Description:

Permission

At present, in stream typeahead in the compose box, we sort pinned streams > subscribed streams > other streams, with message volume serving as the tie breaker.

To improve the likelihood that the desired streams are sorted at the top, we should change the ordering to be:

stream that the message is addressed to (if any) > unmuted pinned streams > unmuted subscribed streams > muted streams > o

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.

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a feature

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I just set up a sandbox project for myself using the new interactive dbt-init. When it asked what I wanted to call it, I chose joel-sandbox.

When I ran dbt debug, it failed because 'joel-sandbox' does not match '^[^\\d\\W]\\w*$'.

Expected Behavior

dbt init should at mi

Current tools docs could be updated to reflect changelog entry regard rtm.start method deprecation for apps created after Nov 30th, 2021.

The page URLs

• https://slack.dev/python-slack-sdk/real_time_messaging.html

Requirements

Please read the [Contributing guidelines](https://github.com/slackapi/python-slack-sdk/

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 "
    },
    {
 

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