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!

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

Usually, next_cursor in an API response exists under response_metadata property. However, only admin.conversations.search API method's response has it at the top level: https://github.com/slackapi/java-slack-sdk/blob/main/slack-api-client/src/main/java/com/slack/api/methods/response/admin/conversations/AdminConversationsSearchResponse.java#L19

Due to this inconsistency, this part in this Py

Describe the bug

Macros are not working in post-hooks in dbt_project.yml but working as a model config

Steps To Reproduce

1. Create an empty dbt project with dbt init
2. Create a macro in macros/grants_test.sql. I'm using this for testing:

{% macro grants_test(rel) %}
ALTER TABLE {{ rel }} SET OPTIONS (description="testing...")
{% endmacro %}

3. Modify the `dbt_pr

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)

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 }) => {