Tell us about your environment:

• Puppeteer version: 1.14
• Platform / OS version: Windows
• Node.js version: 10

What steps will reproduce the problem?
try to pass a promise to await page.waitForResponse(response => condition) instead of urlOrPredicate.

What is the expected result?
expect async function to work

What happens instead?
no waiting as promise

Describe the bug
In the config.js addParameters function, if I set isFullscreen: true and open the webpage, it is fullscreen on startup. But if I set isFullscreen: false and open the webpage again, it is still full-screen on startup.

To Reproduce

1. Set isFullscreen: true, open the webpage,
2. Close the webpage or stop the server
3. Set isFullscreen: false, open the webpa

Given the immense popularity of Docker and the need to harden it different per platform (see ideas below) - we'd like to start writing a Docker best practices section.

You're welcome to contribute ideas and write best practices - writing and brainstorming will people is an amazing way to deepen your Docker understanding.

At first, we want to collect ideas for best practices, solidify a list

Note: This is fundamentally working as intended, this issue is now about validating the config and providing a sufficient warning.

🐛 Bug Report

The configuration testSequencer (https://jestjs.io/docs/en/configuration#testsequencer-string) is silently ignored in projects (https://jestjs.io/docs/en/configuration#projects-arraystring--projectconfig)

To Reproduce

Run this config

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

I'm getting bit with failing documentation builds because I'm writing docstrings that JSDoc doesn't like (specifically, TS-style). But there's no linting happening before getting to Netlify.

We may be able to make JSDoc just check the syntax and exit (and make it part of the lint scripts).

This is moot if we want to move forward with maintaining our own TS types (for which there is an op

Current behavior

Hello, I would simply like to request that the documentation for find() (https://enzymejs.github.io/enzyme/docs/api/ShallowWrapper/find.html) be updated to reflect its snapshot-nature. For example, in a situation where clicking a button updates state under the hood...

   // some set up code goes here. 

    const deleteButton = wrapper.find('[data-enzyme-id

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

Expected Behavior

const sym = Symbol('foo');
expect({}).toEqual({[sym]: 'foo'});

This test should fail. It currently passes.

Current Behavior

The go build command in the Compilation Wiki will throw complaints.

#Compile from source
cd $HOME/gocode/src/github.com/buger/gor
go build LDFLAGS = -ldflags "-extldflags "-static""

$ go build LDFLAGS = -ldflags "-extldflags \"-static\""
can't load package: package LDFLAGS: malformed module path "LDFLAGS": missing dot 

Describe the bug
When TEMPLATE_LIST_TEST_CASE and TEMPLATE_LIST_TEST_CASE_METHOD were added, the corresponding versions with the CATCH_ prefix were missed.

Expected behavior
CATCH_TEMPLATE_LIST_TEST_CASE and CATCH_TEMPLATE_LIST_TEST_CASE_METHOD should be available.

Additional context

The commit that added TEMPLATE_LIST_TEST_CASE and `TEMPLATE_LIST_TEST_CASE_MET

This is a great book and I've enjoyed following it through almost to the end.

However, if I type / copy the code in the first code block at https://quii.gitbook.io/learn-go-with-tests/go-fundamentals/math#write-the-test-first then run the test, it will give me a

Success: all tests pass.

It looks like the package that is being included already has the correct code. The guide should sure

Hi,

It seems like the HTTP Assert package does not allow me to specify a body to pass in a POST request for example. Looking at the HTTPBody() function, the body argument is set to nil:
req, err := http.NewRequest(method, url+"?"+values.Encode(), nil)

Is this by design, or am I looking at a missing feature?

Cheers,

As a new end user, I cannot find a single user guide or decent documentation. The javadoc reads like it's written as a quick review for someone who already knows the ins/outs of Mockito and just need some sample code. I don't even know what or how Mockito works and the first couple of lines are talking about "mockito inline".

Most open source projects have really great user guides and document

• Faker version: 1.0.7
• OS: Ubuntu 16.04

I was wondering if it is possible to generate a list of 'n' unique company names? I saw some PR's which gave a unique keyword for 'words' but doesn't seem to extend to other providers? I understand i could just keep regenerating and dropping duplicates until I got a unique set of length n, but would be nice to just have a keyword for that (plus this m

I'm upgrading a build environment from python 2 to python 3 and noticed that endpoints with seeded random numbers are not returning the same values. It seems to be related to usage of randint:
https://github.com/postmanlabs/httpbin/blob/f8ec666b4d1b654e4ff6aedd356f510dcac09f83/httpbin/core.py#L1448

It seems like randint is not seed safe and it looks like only random() is: https://bugs.python.o

Feature request

I found that phpstan doesn't understand psalms numeric-string type (see https://psalm.dev/docs/annotating_code/type_syntax/scalar_types/#numeric-string)
It would be nice to support it.

here is playground link
https://phpstan.org/r/9e26dfae-706f-4e3a

• I have read CONTRIBUTING and have done my best to follow them.

What did you do?

In Xcode 10.2.1 (iOS 12.4), in order to trigger viewDidAppear logic did the following:

    let viewController = ViewController()
    let _ = viewController.view
    let window = UIWindow(frame: UIScreen.main.bounds)
    window.la

The second example in section 1.1 says:

expect(result.approved).to.be.false;

It should be:

expect(result.approved).to.be.true;

(I'm guessing you made it false so you could simulate the error output in the next picture.)

I have searched the issue list for something similar, but I have not found the exact same issue.

The problem is that, given these two models:

factory :employee do
  # various attributes
end

factory :job do
  association :employee, strategy: :build
end

attributes_for ignores any explicit employee assignments:

attributes_for(:job, employee: some_other_em

Is your feature request related to a problem? Please describe.
This is releated to this.

I believe documentation on the topic of mocking is outdated. I'm quite new to React Native and it took me a while until I figured that current version of metro does not support `r

I thought I'd give some feedback on how the https://reactcosmos.org could be better, I'm happy to help with some of these items, but better to write them down and discuss them first.

• The website works really well as a marketing site right now, but it doesn't really capitalize on that by calling users to action. It should tell them to "Get Started" or "Install" with either a big button to

According to your documentation (https://docs.pytest.org/en/latest/xunit_setup.html), I can name a method teardown() in a test class, and it should not get run by pytest. I am using version pytest-3.8.2.

Pytest calls a method called teardown on class destruction even though it is specified as teardown_class in your documentation. I am guessing this accidentally did not get removed, when the na

This stackoverflow post outlines a different method of using namedParameters than the readme and seems to be correct. Readme could be updated to match.

https://stackoverflow.com/questions/6212219/passing-parameters-to-a-bash-function

Would it be possible to add "trim" parameter to keyword "Should Be Equal As Strings" (+related keywords)?
Many times I need to compare two strings, but there are some trailing or leading whitespaces in the actual value, which I don't care about, so I always have to trim them before. Having trim as a parameter in these keywords would help me a lot :)