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

see #347 for the link being added back to the readme

Right now Node.js's README writes:

var client = foo.bar({
  username: 'pksunkara',
  password: 'password'
});

Is it possible to change it to:

var client = foo.bar({
  username: 'api_key',
  password: 'api_secret'
});

Currently, when we test different transports (tcp, unix socket, etc etc), we run the full test suite:
https://github.com/docker-java/docker-java/blob/21583b51e02c129ead0732fbe235d02eb608e341/.travis.yml#L24-L43

However, it is enough to run a subset that can be affected by changing the transport.

This should dramatically improve the CI times and make it more stable.

https://github.com/nsqio/go-nsq/blob/3c0c5ed026c3a4b2ecc62c675fd4579c2ca65d16/consumer.go#L781-L786

If FullJitterStrategy calculates a value less than config.MaxBackoffDuration then backoffCounter will increment where ExponentialStrategy wouldn't, potentially causing inBackoff() and RDY 1 to persist longer than intended.

This probably matters very little for most use cases, but durin

When entering 2FA password it is shown in plain text. This is because it uses input:

https://github.com/pyrogram/pyrogram/blob/945bc61262f3cad9fa15a441a3834e1819cedd39/pyrogram/client/client.py#L711-L712

I suggest to replacing it with with getpass.getpass().

This should be an easy fix and I think it could be helpful for user looking to create a new branch.

createReference is passed three arguments:
ghrepo.createReference('master', '18293abcd72', callback);

The first argument should be the new branch name.
The second argument should be the SHA-1 hash value of the commit to branch off.

A better example would be as follows:

    // get th

Currently there is no way to update the pull request with the latest upstream changes, when using the library. Github has provided a REST endpoint for it - https://developer.github.com/v3/pulls/#update-a-pull-request-branch

It will be good use case to add to the library.

If you survive a round, a yellow crosshair becomes visible in the center of the regular crosshair. It disappears if:

1. You die.
2. Turn off crosshair from adv. controls.
   Any suggestions how to fix it?

Self explanatory, grossly negligent

I'd like the documentation to explain what the differences between the synchronous and the async reader examples is. The might be obvious to those who developed pynsq, but aren't necessarily to somebody looking at it from the outside (like me).

Thanks!

Thank you for this great crate. I start using it today.
As for the pub/sub examples in Readme.md, they cannot communicate with each other, because one publishes as String and the other subscribes as UInt64.
How about editing the subscriber so that it subscribes as a string.

Several users have asked for the ability to use the library without composer. One example would be for simple standalone scripts. We need to investigate what's involved and add docs/update code as necessary to address.

Is it useful to identify errors by source in catch clauses. One common solution is to emit subclasses of Error. Another is to fill an identifying field on the error object. Either way, the chosen option should be a documented part of the client's interface.

node-sparkpost currently produces error instances with error.name === 'SparkPostError.

A few options:
[ ] - Publish the `.name =

Is there any specific reason why this package has not been submitted for inclusion in the 3-day doc builder cycle on the farm? Searching for rosnodejs in the Kinetic distribution.yaml yields no results, and the wiki page appears to have the package header h

See the Ably SDK IDL, specifically TO3b and TO3c.

Ably JS does not support attributes:

• logLevel
• logHandler

I propose we introduce those attributes, and remove log in a 2.0 release.