-
Updated
Nov 30, 2021 - JavaScript
slack
Here are 5,140 public repositories matching this topic...
-
Updated
Dec 1, 2021 - Clojure
-
Updated
Nov 30, 2021 - TypeScript
-
Updated
Nov 30, 2021 - TypeScript
-
Updated
Nov 14, 2021 - JavaScript
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
-
Updated
Nov 30, 2021 - Go
Describe the bug
The button to toggle the chat widget doesn't have discernible text.
To Reproduce
Steps to reproduce the behavior:
- Go to a page with the Papercups chat widget installed.
- Check accessibility with axe DevTools
- See
Buttons must have discernible textissue
-
Updated
Nov 21, 2021 - JavaScript
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
During the execution of a snapshot, the timestamp used for the dbt_updated_at, dbt_valid_from and dbt_valid_to columns is not consistent between the inserted, updated and deleted rows.
For the [inserted](https://github.com/dbt-labs/dbt-core/blob/a9b4316346e3c25b82fc59fa1f090e14
-
Updated
Jun 1, 2021 - Python
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 [ ])
- [ ]
By default axios has no timeout, this is a bad default for production systems and currently there is no way to override it.
You can override the socket timeout with the agent but it's not the same thing.
I would like to be able to change that via the WebClient options.
Note: This was added for web-api in slackapi/node-slack-sdk#1250
As a part of this issue, it'd be
-
Updated
Aug 5, 2021
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.
I've noticed that some of our alerts where failing with the following error message:
Failed to send an serviceAlert for service=Very Cool Service "ServiceYXZ": call to provider alert returned status code 400: Bad payload received by generic incoming webhook.
It seems the issue is caused by unescaped quotes (") in the HTTP POST - in this specific case in the text property:
``
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
-
Updated
Mar 26, 2020 - Swift
-
Updated
Jul 30, 2019 - CSS
Improve this page
Add a description, image, and links to the slack topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the slack topic, visit your repo's landing page and select "manage topics."
In
delete_realm_export, we assert that the export hasextra_dataon it:https://github.com/zulip/zulip/blob/30f2d50f1f5255ee3c3200d6f88ba8dbea6bc4dd/zerver/views/realm_export.py#L94
This is only set after the export is complete:
https://github.com/zulip/zulip/blob/30f2d50f1f5255ee3c3200d6f88ba8dbea6bc4dd/zerver/worker/queue_processors.py#L1000-L1006
The combination of these means that