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'                               

When using the url http://docs.python-requests.org/en/latest/, it redirects to https://2.python-requests.org//en/latest/ (notice the extra / before en). This causes a HTTP 404.

Expected Result

The redirect should be to https://2.python-requests.org/en/latest/

Actual Result

HTTP 404

Reproduction Steps

Try to visit the latest en documentation for requests using the

I want to use the SFTP protocol to create folders on the remote SFTP server, without specifying the curl option. The option created on the FTP protocol is "CURLOPT_FTP_CREATE_MISSING_DIRS".
Do you have any corresponding SFTP options?
Thanks for any help.

Hi team!
I'm trying to run the API generator for a new API with a private discovery document. However, I'm running into a few issues.

• I can't find documentation on how to run the generator. I think it would be really useful to write this down somewhere in a README. I don't use this package enough to remember the commands.
• I'm not able to generate after a clone, npm i, and `npm run gener

I think the work you've done on this is amazing. Seems like a great project, but your README is a bit bloated and hard to decipher. Might I suggest you condense it down into a set of readable chunks and maybe link off to the wiki for the more detailed bits.

Its only my opinion, but I find that answering the following questions, in order, helps to simplify docs.

• who? - who wrote the p

See openethereum/openethereum#11542 (comment).

After we migrate all wiki to OpenEthereum org, we need to update all the links in README.md and CONTRIBUTING.md here.

Describe the bug
Docs never mention that Vibora searches for a folder named templates, additionally template rendering varies depending on where from you execute the file.

To Reproduce
Given the following folder structure:

.
├── project1
│   ├── app.py
│   └── templates
│       └── index.html

When Vibora is run from root folder like so python3 project1/app.py it wo

Some command outputs don't look great on a dark background:

Originally reported in donnemartin/saws#18 by @sesas

We are missing the query parameters in the doc example generator.
For instance the example f8cc4b331a19ff4df8e4a490f906ee69 is missing the v parameter as query string: GET /_cat/health?v (see [here](https://raw.githubusercontent.com/elastic/built-docs/master/raw/en/elasticsea

Does YakYak use system-wide certificate store such as Chrome? If so, possible injection of root certificate in the system may have serious implact on security inluding MITM. I think YakYak has to use own cert store with only trusted root certificates. The confusion can be because user does not percieve messenger is using same communication mechanism as browser. The second thing is that user may us

Context
would be nice to have a feature to disable showing the public internet servers... keep them from populating. i run this as a lan voice chat as intended and some of the server name/descriptions are not appropriate for kids... Nothing against free speech and all but i prefer to have some means of not corrupting my kids to early.

Describe the feature you have in mind
check box

1. Share good stories. Enhancement - share link by email
2. Send to mobile. Enhacenement - use pushbullet api to push link to user's phone
3. Send to Text-to-Speech reader on android - I use " @voice " on my android to have HN articles read to me while I drive. Can we push article links using pushbullet api to your phone and to your TTS app?

Elasticsearch version : 7.6.0

elasticsearch-py version : 7.5.1

Description:
Since Transport._get_host_info(self. host_info) can not handle IPv6 address, sniffing fails to get a list of nodes upon startup.

ScrollAllObservable and associated methods are an observable implementation that uses the scroll API to fetch all documents matching a query, supporting concurrent scrolls through slicing. Documentation should be added to demonstrate its usage, and a link added to the Elasticsearch reference documentation to point to those docs.

HTTP.get(nil)
HTTP::Request::UnsupportedSchemeError (unknown scheme: )

HTTP.get('')
HTTP::Request::UnsupportedSchemeError (unknown scheme: )

HTTP.get('/')
HTTP::Request::UnsupportedSchemeError (unknown scheme: )

HTTP.get(':')
Addressable::URI::InvalidURIError (Cannot assemble URI string with ambiguous path: ':')

Ideally it should return InvalidURI exceptions if the URL is

ex:

	req := esapi.DeleteRequest{
		Index:   indexName,
		DocumentID: doc.DocID(), //404 ID
	}
	res, err := req.Do(ctx, es.esClient)
	if err != nil {
		return err
	}
	// read the entire body so that the connection can be re-used
	_, _ = io.Copy(ioutil.Discard, res.Body) // does not return error
	res.Body.Close()

	if res.IsError() {
		es.logger.Log(
			"message", "could not de

https://pika.readthedocs.io/en/stable/examples/tornado_consumer.html

Running this example throwed TypeError (exchange must be a str or unicode str). And this is caused by the sequence of positional arguments.

def setup_exchange(self, exchange_name):
        """Setup the exchange on RabbitMQ by invoking the Exchange.Declare RPC
        command. When it is complete, the on_exch

The comments around from_seed_slice specify that this is a dangerous method only to be used for testing, however the upper of Pair uses it without that information passed on and the client is using the same functionality to generate the tests keys for Alice, Bob, etc.

We should clarify the documentation to clearly stated under which circumstances this features is to be expected to be us

When releasing a new version it's always hard to deliver a proper changelog. Keep a changelog is a proposal on how we can deliver a consistent and complete changelog.

I propose we implement it in this repo. I would require the following steps:

• Refactor the changelog to the keep a changelog spec.
• Add up

Feature description

Very apparent when nicklist is horizontal: /set weechat.bar.nicklist.position top

When there's many people on one channel, the longest nick slot is used to properly space names in the nicklist . In normal case it works well:

@me  b   d   f   h   j   l   n   p   r   t   v   x   z
 a   c   e   g   i   k   m   o   q   s   u   w   y
-------------------------------

Instead of always allocating a fixed size buffer (1,000,000 bytes currently), it should leverage the upfront knowledge of total size of the metadata and allocate Math.min(DEFAULT_BUFFER_LEN, metadata.length()).

This reference to golang documentation is completely wrong:
https://github.com/gocql/gocql/blob/e6d89e6c5ab3faf5127fc95fb85477f39ac9c792/conn.go#L764-L766

Original documentation says:

WriteTo writes data to w until there's no more data to write or when an error occurs. The return value n is the number of bytes written. Any error encountered during the write is also returned.

https://gola