Brew is listed as the recommended way of installing httpie on macOS. However, it doesn't work with auth plugins.

For example, if you pip3 install requests-hawk and then run http --help hawk will not show as an auth type. If you pip3 install httpie-oauth it will install httpie via pip as a dependency and overwrite the brew installed link in /usr/local/bin/http and now all the plugins wil

🚀 Feature request

To help with diagnosing ngcc issues it would be really useful to be able to see the debug output from ngcc. Could we expose these logs, perhaps when the CLI is in --verbose mode?

Command

• build
• serve
• test
• e2e

As far as I can tell bat as a library only supports writing to stdout, I'm interested in seeing if I can integrate bat with color-backtrace/color-spantrace and eyre. To do this I need bat to write to a std::fmt::Formatter and return a fmt::Result instead of printing to stdout (i assume?) and returning a bat::error::Error.

So assuming I'm not misreading the docs...

Proposal

Hi, I've found the following cheatsheet :

In the README you explain that there must be an edit button in the page and a github button to access the sheet but as you can see it doesn't appear here.

Thx ;)

Spurred by conversation in avajs/ava#2449 and avajs/ava#1485 we'd like for our assertions to return booleans. true when they pass, false when they fail. This does not apply to the throws() and throwsAsync() assertions.

Failing assertions will fail the test, but do not throw exceptions. This means your test does not stop executing. Usua

Note: Given a little bit of guidance on what formats are supported, I'm available to contribute to the below and/or create a PR.

User Story:

As a developer using Fire, I would like to have a page or section in the Fire documentation here and/or here which gives guidance on which docstyle formats are s

As I understand this is a rebranding of the enclose module? Would love to know how this happened btw.

But, in original documentation, here – http://enclosejs.com/#compilation-srsly it says that resulting binary will be at least 2x slower, is that still the case? And if so, can you mention that in the readme? It would be better I think to also document how this sort of measurements was perform

"Flag provided but not defined" doesn't give enough details for end users who aren't specifically aware of how CLIs work. I get a lot of bug reports that are "I got this obscure error message, and I'm not sure what to do".

See also

• urfave/cli#663
• urfave/cli#744

When I run fd, I get this:

[1;34mext\ [0mphp_mbstring.dll
php7embed.lib

I think fd should automatically detect when the user has a terminal without
ANSI support, and disable colors.

See vadimdemedes/ink@a056565 for context.

...this boilerplate is awesome, thank you for sharing it guys 👍

Hi there

I'm trying to parse this king of lines, from a python flask service whose log format is %(asctime)s [%(process)d] (%(levelname)s) (%(name)s): %(message)s

2020-02-10 13:58:38,594 [31383] (INFO) (flask.app): request: OPTIONS https://server_hostname/0.1/token/a_big_uuid {'Host': 'server_hostname', 'X-Script-Name': '/api/auth', 'X-Forwarded-For': 'an_IP_address', 'Connection': 'c

Currently, each argument to fx treated as an anonymous function. Here is an example:

fx 'groupBy("commit.author.name")' 'mapValues(size)' toPairs 'sortBy(1)' reverse 'take(10)' fromPairs

But this requires a lot of ' quotes. My idea is to split the argument by whitespaces . So next will be possible to write:

fx 'groupBy("commit.author.name") mapValues(size) toPairs so

Some of our wiki pages are outdated. User manual or developer guide type information should move into the sphinx docs for better visibility and so that it's versioned with the code. I think it makes sense to use the wiki for longer-term planning or planning of big changes, with the target audience being beets contributors. Where possible smaller plans can go to issues on beets with appropriate lab

First of all, thank you for maintaining this wonderful project!

We've been running CI tests on our product that uses click, and tests for command-line stumbled upon a change in output representation [introduced](pallets/click@718485b#diff-fb2a32ceb27b1c3d30b386fbae56f34eR

What happened:

I tried to use the --make option to pass --jobs=5 to the NodeJS build process.

What you expected to happen:

I expected the NodeJS build to be faster.

What happened:

I was unable to pass the jobs options to the NodeJS make command, here is what happened:

➤  nexe --build --make --jobs=5
ℹ nexe 3.3.2
✔ Node source extracted to: /home/thibault.hi