Current behavior:

We use --env variable to pass some environment variables to cypress, when it's running both in headless and headed mode.

One of the parameters is a hash (mix of numbers and characters). Surprisingly some specific hash values make cypress to fail reading this value from the command line (e.g. 769e98018). The corresponding environment variable is not set and the `Cyp

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

There doesn't seem to be coverage for redeclaring "arguments" in direct eval in function parameter expressions. For example:

function f(p = eval("var arguments")) {}
f();

should throw a SyntaxError when evaluating EvalDeclarationInstantiation in step 5.d.ii.2.a.i.

I've written some basic tests at <https://phabricator.

Is your feature request related to a problem? Please describe.

I'm trying to get two containers to communicate with each other.
I can start up each container and connect to it from the command line using localhost and the bound IP but I'm not clear how to get two containers to talk to each other.
I think this would be the equivalent of "docker network connect" https://stackoverflow.com/qu

@nodkz i ask because this project is currently very mixed in this case and we should standardize it with an eslint rule to make it always surrounded or let it removed

In our tests we often validate default data and prop values for the component under test using something like this:

componentUnderTest.data().should.deep.equal({
 // all expected data values go here
});

componentUnderTest.propsData().should.deep.equal({
 // all expected props values go here
});

We're using v4.2.0 and this works nicely for calls to data(), and it do

Right now, [README.md][readme] includes copy-pasted code from sample code in [src/example/][src/example] tree, but they're not kept in-sync automatically.

Ideally, we would have a process for automatically including code samples, e.g., via some preprocessing since it's probably not possible to do it dynamically, so that we can avoid having to see them diverge, e.g., as can be seen in issue

Righ now we have a Java sample app, we should show the usage of the app in a Kotlin example also.

The docs are currently written for someone familiar with jest mocha and Enzyme.

1. Perhaps add at the beginning:

Specs is an addon to Storybook.
Storybook allows the developer during development to visually see a component or part of it, and interactively see immediate changes to the code. It also helps document the project with visual examples.
Specs adds the ability to

What does this mean? I generated the map just before using it... but noted that the version field in my .yml file is blank...maybe that?

Also - on your documentation page, you might change
bundle exec crystalball
to
bundle exec crystalball spec

Here the config I am using for jest in jest.config.js:

module.exports = {
  transform: {
    '^.+\\.jsx?$': 'babel-jest',
    '^.+\\.ts?$': 'ts-jest'
  },
  rootDir: './lib',
  roots: ['<rootDir>'],
  moduleFileExtensions: ['ts', 'js', 'json', 'node'],
  preset: "@shelf/jest-mongodb"
};

Jest fails to run tests just saying "Determining test suites to run..."

Works if

Now that @ember/test-helpers implements the majority of this addons APIs, we should make it clearer in the README that folks should likely use @ember/test-helpers whenever possible.

To reproduce it, run pytest in this repo:

tests/test_pytest_picked.py: 13 tests with warnings
  /home/ana/workspace/pytest-picked/venv/lib/python3.8/site-packages/pytest-5.4.1-py3.8.egg/_pytest/terminal.py:287: PytestDeprecationWarning: TerminalReporter.writer attribute is deprecated, use TerminalReporter._tw instead at your own risk.
  See https://docs.pytest.org/en/latest/deprecation

The ELM Architecture handles HTTP requests outside of the mount function, as it considers them impure.

Do we simply execute the request inside of the update switch statement i.e. break the pattern?

Following functions are missing from the Functions\stubTranslationFunctions():

• _n()
• _nx()
• _n_noop()
• _nx_noop()

P.S. Happy to send PR, if the suggestion looks good.
P.P.S. Documentations seems to be the out of the sync.

https://blogs.technet.microsoft.com/secguide/2016/10/02/the-mss-settings/

Make the output, especially as generated by the macros TEST_CHECK(), TEST_MSG() and TEST_DUMP(), automatically adapt to the current terminal size, so that it looks good in a reasonably small terminal window but can use effectively more space if the terminal window is big.

This should involve:

0. Explore what API is available for the purpose on the platform of your choice.
1. A pre-pro

Our README rocks! It's very complete and clear in every sense, but I think it's a bit too complete.

At least in my opinion a README file should only summarise what the project is about, how to install it, give like 1 or 2 examples, who are the project administrators and how to contribute.

Since this file already has examples for each of the methods we've created so far (or most of them maybe