In = syntax,

• double quotes (")
• back slashes (\)
• non-ascii characters

are escaped in json.dumps:

$ http -v httpbin.org/post                                      \
    dquote='\"'                                                 \
    multi-line='line 1\nline 2'                               

• nvim --version: NVIM v0.5.0-23-gafd576ee9
• vim -u DEFAULTS (version: ) behaves differently? yes
• Operating system/version: Ubuntu 18.0.4.1 via WSL
• Terminal name/version: conhost
• $TERM: xterm-256color

Steps to reproduce using nvim -u NORC

Download:
[neovim_enc_bug.txt](https://github.com/neovim/n

Operating system: Any
Last upstream commit (run git log --author="Robert Lord" | head -n 1): commit cf29f6786c288b6111239b8e8b211f8ae2fbc4c3
Browser version(s): Any
Ruby version (run ruby -v): ruby 2.3.3p222 (2016-11-21 revision 56859) [x64-mingw32]

We started seeing either an 'undefined' or a blank space in our page titles, as some of the headers have nested html, and the Slate

Describe the bug
Find-one endpoint /resource/:id responses with 500 status code instead of 404, this happens with MongoDB setup.

Steps to reproduce the behavior

1. Setup Strapi with MongoDB configuration.
2. Create a collection (resource).
3. Give findOne access to the public.
4. Send a request to /resource-name/any-invalid-id.

Expected behavior
404 response.

**Sys

Jumping to a subsection via the sidenav will sometimes cause the page header to overlap the anchor point. When navigation is working correctly, there's a perceptible flicker/jump, so I'm guessing javascript is being used to calculate the offsets. Looking at mkdocs's docs, this isn't an issue. I'm wondering if this is something that will be fixed by upgrading mkdocs (#6623), or if it's a theme issu

Description

How can I use socket.io instead of the plain websocket integration? I guess this is more a question belonging to starlette.

Currently migrating from a flask application using flask-socketio / python-socketio

Any hint is appreciated. Thx.

While ccxt does a great job unifying most functions / settings, not everything is or can be unified.
I think it would be good to provide a separate wiki/documentation page which documents exchange-specific properties.

The behavior is there now and all is working well - but to find it users need to search through issues (which are not easy to navigate) to find certain exchange-specifics - and o

Is your feature request related to a problem? Please describe.
An external API does not always respond successfully. Server errors for example 50x or 429 Too Many Requests may occur. Manually pressing the send button while waiting for a successful response can be tedious.

Describe the solution you'd like
Be able to set the number of retries and the expected/unexpected status codes o

Custom error formatter must have now 5 arguments instead of the old 4. These changes were introduced here on #1652

When migrating from 0.19 to 1.1.0 I had issues on a custom error formatter because the original_exception argument was introduced but that change was not documented on the upgrading guide.

I want to translate the Web3.js document into Korean. (We have confirmed that the translated document does not exist so far.)

May I take charge of this work?

And if possible, I would like to know if there is a guideline in the translation.

I'm going to use ReadTheDocs, and I'm thinking about whether it's better to PR in the Web3.js Repo or make a separate repo.

If any of you who are lo

Currently, we ask contributors to strive for consistency with existing code, but it would be helpful to clarify the following regarding docstrings:

• Docstrings should begin with a short (~70 characters or less) summary line that ends in a period.
• The summary line should begin immediately after the opening quotes (do not add a line break before the summary line)
• The summary line should de

Prerequisites

• I am running the latest version. (up upgrade)
• I searched to see if the issue already exists.
• I inspected the verbose debug output with the -v, --verbose flag.
• Are you an Up Pro subscriber?

Description

It would be great to add regex capabilities to redirects like so:

redirects: {
  "/folder/:slug(regexhere)": {
    "location": "https