Doc about endpoint testing states:

If you start your server using a test.before() hook you should make sure to execute your tests serially

This is not clear to me why is better to have tests in serial in that case. Anyone can explain me?

You can always make a suggestion as an issue tab for apps that are not on the list. I will personally check out the app and verify if it is working, properly mantained, safe to use (as a user not a security expert).
Translation is very much appreciated. You can either fork this and remake your own translation or use the same repo with me. I highly recommend translator to review the commit log e

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

Currently fkill-cli is only listing 4 processes, but the screen can be much larger. Any reason to only list 4 lines?

I just removed bower-name-cli, which was the first entry in web development, but has been deprecated for 6 months.

We might want to check all legacy cli and determine whether they are still:

• maintained
• relevant

There is an issue with the latest version 6.0.0 of np after the package is published it tries to do 2fa and it fails. The account doesn't have 2fa enabled, as well as npm repo. Also, the package is published and then it tries to do 2fa, that seems strange I would expect 2fa is a step before publishing.

Description

Commit Range:
v0.4.0...master

Registry:
https://registry.npmjs

The Carbon CLI is really awesome and I love that it's possible to store and reuse a configuration as preset. One thing I'd love to add to the config though is the actual "theme colors" (i.e. what color e.g. variables, operators, keywords, comments, ...).

Basically these options from the Carbon web UI:

![Screenshot 2019-03-26 at 10 39 45](https://user-images.githubusercontent.com/4058327/5498

This is more of a development problem and does not affect users as it is with dev dependencies. When cloning the repository and running yarn, yarn warns about incorrect peer dependencies:

$ git clone https://github.com/apiaryio/dredd.git dredd-clean
Cloning into 'dredd-clean'...
remote: Enumerating objects: 54, done.
remote: Counting objects: 100% (54/54), done.
remote: Compressin

Describe the bug
Observe how exceptions thrown from actions:

• The message from the exception is logged as an error
• The process is exitted with process.exit(2).

The above works correctly, when logging the error is synchronous, however it does not work when logging the error is asynchronous. [The node.js do

It would be nice to have a function to auto create dev users (one user per defined role) for example in the schema:

dev_administrators - password: dev123456 - example dev.administrators@example.com - Name: "Dev user - password is dev123456"

In the /examples folder have more practical examples in separate files, for example, in the smod project:
https://github.com/enddo/smod

SMOD > show modules
Modules Description

modbus/dos/arp

There are currently several places in the language where we accept arbitrary expressions:

1. In the clause of where
2. In the argument of aggregates (sum(xyz)),
3. In the group-by clause of aggregates (* | count by status_code > 500, response_ms < 300, url)

The set of arbitrary expressions that can be constructed is growing, and it'd be great to have those documented separately where

We need a proper website, with docs, examples, etc.
Basic static generation (e.g. with Gatsby) from markdown (to allow for current docs reuse) would probably work just fine.

I suppose this could be just a change to the readme to correctly describe the default behavior, but there is currently no way that I can find to make help the default for the expand type.

prog
  .command('foo')
  .describe('Top level command')
  .action(() => console.log('see `app foo --help`'))

prog
  .command('foo bar')
  .describe('A subcommand')
  .action(() => console.log('did a thing'))

Use case: the foo command doesn't do anything and requires usage of subcommands. As it is, doing app foo --help does not display any possible subcommands under the

Magento caches a map of controller actions.
If a controller action is added, the whole config cache must be flushed.
This command should flush only the entry of the action list.

Currently this happens

tabrindle-mbp:~ tabrindle$ solidarity imdumb
ERROR: No solidarity file was found
Make sure you are in the correct folder or run solidarity snapshot to take a snapshot of your environment and create a .solidarity file for this project.

Many CLI tools like commander have a simple option to forward unrecognized commands to help - does https://github.com/infini

I find the highlighting of the test summary confusing when there are failures:

Pass:

Fail:

• Is it possible to use a neutral color for `testing: warning: no tests to run