Figured out this issue when solving upon a similar one , regarding the error thrown when a owner/admin , while adding a new custom emoji accidentally leaves the emoji_name field blank. (Also fading the Add emoji button , unless the user manually reloads it)

Screenshot :

![Screenshot from 2020-12-18 23-02-08](https://user-images.githubusercontent.com/53977614/10

It's useful to know. This request came through support.

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

After #771 was merged, the files_upload function signature still does not accept a bytes type object: https://github.com/slackapi/python-slack-sdk/blob/main/slack_sdk/web/client.py#L1458-L1460

    def files_upload(
        self, *, file: Union[str, IOBase] = None, content: str = None, **kwargs
    ) -> SlackResponse:

So the OP example produces a mypy error: `Argument "file" to

Description

It's a best practice to always provide a text argument when posting a message, even though the platform doesn't technically require it when blocks are provided. The text argument is used in places where blocks cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.

In order to help apps adhere to this best practice and

Problem
We need to be able to calculate how long it takes for a conversation to be closed ("resolved").

Right now the way we determine if a conversation is closed is by looking at the status field, which can currently only be "open" or "closed".

Solution

• Set up a database migration to add the closed_at field to the conversations table (as a utc_datetime)
• Update the

Describe the feature

Reduce the BigQuery OAuth scopes down to the minimal set needed, in both dbt and dbt Cloud.

Additional context

Currently, the dbt BigQuery connector requests these three OAuth scopes:

• 'https://www.googleapis.com/auth/bigquery'
• 'https://www.googleapis.com/auth/cloud-platform'
• 'https://www.googleapis.com/auth/drive'

The BigQuery scope is needed to a

Description

This repository's TravisCI build settings no longer work. We are planning to migrate to GitHub Actions before the next release.

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

• bug
• enhancement (feature request)
• question
• documentation related
• testing related
• discussion

Requirements (place an x in each of the

I try to switch from RamBox to Ferdi. However I have several services with the same icon (slack, nextcloud). It would be a great help if I just cloud add a small textual label next to, under, over the icon. Don't care where.

Sorry that this is not a pull request, my JS/css knowledge is insufficient. I tried copying the tooltip to a div. Didn't get the correct tooltip and a misplaced div...

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.