Description:

Whenever I change any of the room info (description, announcement, etc.) this resets the room setting which is supposed to hide system messages.

Steps to reproduce:

1. Go to "Room info" in a channel where you have privileges to change the room info.
2. Toggle on the "Hide system messages" setting. Confirm that this change itself is not posted in the channel.
3. Close

Create an incoming webhook integration for Patreon. The main use case is getting notifications when new patrons sign up.

Patreon webhook documentation: https://docs.patreon.com/#webhooks

Now that Zulip has a Patreon page, it would be great to be able to monitor new sign-ups!

A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Have a facepile with exactly 7 users
2. The UI will display 6 avatars and a (+1)
3. This is clearly useless

Expected behavior
Never display (+1)

Screenshots
If applicable, add screenshots or videos to help explain your problem.

![image](https://user-images.githubuserco

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

Problem
Right now if you enter a phone number without the area code or have the wrong formatting in phone number section it will fail silently and not work. We should make sure that there is a country code and that it can work regardless of the text formatting

<img width="534" alt="Screen Shot 2021-05-05 at 5 30 52 PM" src="https://user-images.githubusercontent.com/4218509/117211941-a697de

As a few Socket Mode related tests started failing only in the GitHub Actions environment, I've disabled them by this commit: slackapi/python-slack-sdk@75b554a

We would like to get the tests back to the running tests in CI builds once we figure out the way to make them stable.

Category (place an x in each of the [ ])

• [ ]

Describe the feature

The fine folks at BigQuery have been releasing a lot of solid SQL-standard syntax of late, which means a lucky contributor gets to delete a bunch of code.

The most obvious candidates to me are create schema and drop schema, which no longer need to be python methods—in fact, they no longer need to be `bigquer

Description

Node.js 16 is now available.
https://nodejs.medium.com/node-js-16-available-now-7f5099a97e70

We can start testing with the runtime.
https://github.com/slackapi/node-slack-sdk/blob/d4e89b7270c07423656f7a6fea52782345aa9254/.github/workflows/ci-build.yml#L20

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

• bug
• enhancement (feature request)

There are currently download options for Arch, RPM, Ubuntu, Linux AppImages, Mac, and Windows, but is there any plans to bring it to FreeBSD?

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.

Description

As we implemented in Python and Java, we can provide the similar guidance log messages in Bolt for JS.

$ npx node app.js
⚡️ Bolt app is running!

Unhandled request ({"event": {"type": "message"}, "type": "event_callback"})
---
[Suggestion] You can handle this type of event with the following listener function:

app.event("message", async ({ body, logger }) => {