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 did this

Using curl with alt-svc support compiled in:

$ curl --alt-s

The authentication section describes service-to-service auth:

Service <--> Service - In this model, your application talks directly to Google APIs using a Service Account. It's useful when you have a backend application that will talk directly to Google APIs from the backend.

The "Learn more" link goes to https://github.com/googleapis/google-api-nodejs-client#service-to-service-authenticat

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

• Parity Ethereum version: 2.4.5 or 2.4.6
• Operating system: Linux
• Installation: binary from Github | releases
• Fully synchronized: both, no and yes
• Network: ethereum
• Restarted: yes

Actual behaviour

When starting parity 2.4.5/2.4.6 in archive mode (tracing on, db_compaction ssd, pruning archive, fat_db on) with the default settings for the cache_size

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

Per #68, and specifically this comment by @donnemartin, it would seem this project is, or means to, deprecate in favor of aws-shell

I still see folks open issues & PRs for this, and perhaps the time has come to place a deprecation notice at the top of the README to discourage that.

Currently, the SerializationError and DeserializationError make easy to understand what went wrong, but not why.
The bad object/string is not part of the error, which makes more complex the debugging experience.

This can be easily improved by adding a data field to both the error classes:

class DeserializationError extends ElasticsearchClientError {
-  constructor (message) {

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

As demonstrated here....

Whenever I click on an image in a chat, or someone's profile icon, or any hyperlink in a chat message, the link opens as normal but that "About YakYak" popup appears every single time.

On YakYak v1.5.0, Windows 10 64bit version 1703 build 15063.0

When I try to change the color of items to none, in the first run it works fine then the next one it goes back to the default config.

Mumble-Client.

It would be nice if it would be possible to give others users(only seen by yourself) nickname next to the username, so people can be fastly recognized even if they e.g. have a username which is similiar to another users username.

Suggestion:
This can be set by right-clicking the users name with an entry called "Set nickname".

Then name would like the following in the UI:

The formatted documentation on readthedocs.io (https://elasticsearch-py.readthedocs.io/en/master/) is not showing recent updates, and still refers to 7.0.0 as a development version.

A number of users are asking how to mock/stub/unit/integration test using the client.

It would be good to have a story (unit-testing.md?) where we can point users, and potentially look to release this as a blog post in order to reach a wider audience.

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

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

Issue

When adding a document to Elasticsearch (v7.0.1) using go-elasticsearch on master branch, it is not possible to use the '/' as a separator within the document ID field e.g. title/test.txt.

Sample code:

func example() {
	client, _ := es.NewDefaultClient()
	docID := "title/test.txt"
	req := esapi.IndexRequest{
		Index:      "test",
		DocumentID: docID,
		Body:       strings.N

Both staking and elections should not allow duplicate candidates, but still, it happened paritytech/substrate#4592. A simple fix should make sure that phragmen is internally also dealing with this, in the proper way. Currently, out of luck, the dupes are being ignored, but it should be done in a more mature manner.

There's no need to allocate new byte array for each storage unit being visited. Also, we should use java.security.MessageDigest.update(java.nio.ByteBuffer) instead of update(byte[]), so that the call to Arrays.copyOfRange is not needed.

Feature description

It would be useful to have the ptr to the bar_window we just clicked, I would like, in particular, to get value of scroll_x and scroll_y. Is it possible to add that to the focus hashtable?

Goals:
Simple API to allow user registration and documentation "How do I - user registration".

Non goals:
Implement registration within xmpp.js.

References:

• XEP-0077: In-Band Registration
• XEP-0158: CAPTCHA Forms
• [XEP-0389: Extensible In-Band Registration](https://xmpp.org/extension

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

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