test-source-map fails on Windows 10. Looking at the test file, there is a special case for Windows that is not being met under certain conditions. I believe it has to do with how git is configured to handle line endings on checkout but I still need to confirm

C:\Users\jasne\Projects\node>Release\node test\parallel\test-source-map
assert.js:93
  throw new AssertionError(obj);
  ^

Bug report

Describe the bug

exporting pages that contain

<Link href="#hash"><a>text</a></Link>

when exportTrailingSlash: true is set in next.config.js produces links like

<a href="/#hash">text</a>

instead of

<a href="#hash">text</a>

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1

Following the instructions in the readme:

If the above doesn't fix the problem, you may try the following:

• Open your .bash_profile (or ~/.zshrc, ~/.profile, or ~/.bashrc) and add the following line of code: source ~/<your_profile_file>. E.g. source ~/.bashrc or source ~/.zshrc.
• If the above don't work, try adding the [snippet from the install section](#profile_snipp

What's going wrong?

I discovered this default behavior of PM2 by trial and error:

1. -out logs and -err logs will default to output in ~/.pm2/logs, unless and only unless they are [rerouted](http://pm2.keymetrics.io/docs/usage/lo

I'm submitting a...

[ ] Regression 

If specify non-existed file with --file option, mocha throw expection.

./bin/mocha --file non-existed
/Users/mocha/node_modules/yargs/yargs.js:1163
      else throw err
           ^

Error: Cannot find module '/Users/mocha/non-existed'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
    at Function.Module._load (internal/modules/cjs/loader.js:508:25

#1947 landed a new t.try() assertion. It's experimental, one of the reasons for which is that we don't have documentation yet.

We need to document the assertion, how to use it and what the edge cases are.

Apologies for how bare this issue is — happy to elaborate more if you're looking to contribute this 😍

Could you implement those function inside the validator ?
Those would be very usefull .

Thank you .

On Windows10 machine, following README installation instructions:

c:\code\mean>npm start

mean@2.0.2 start c:\code\mean
concurrently -c "yellow.bold,green.bold" -n "SERVER,BUILD" "nodemon server" "ng build --watch"

[SERVER] [nodemon] 1.18.9
[SERVER] [nodemon] to restart at any time, enter rs
[SERVER] [nodemon] watching: .
[SERVER] [nodemon] starting node server
[SERVER] ../.

I see some other issues that mention this in the comments, but no issue specifically for this request.

I ran the latest intaller (v1.1.0) on Windows 10 Pro (64-bit) and I observed that the symlinks and various environment variables were created. However, I could only run the nvm command in an administrator cmd prompt. Also, after installing any version of Node.js, no cmd prompt could locate the

https://docs.nodebb.org/configuring/databases/

Is there an overview, how the config object for the constructors of the neural network are defined?

This would be interesting:

• Has brain.NeuralNetwork and brain.recurrent.RNN the same config attributes?
• What is the description of the inputSize attribute?

Thank you for the great work with this library, it is realy amazing!

Node version (or tell us if you're using electron or some other framework):

12.1.0

ShellJS version (the most recent version/Github branch you see the bug on):

0.8.3

Operating system:

Windows

Description of the bug:

sed is applied only once by line:
original archive:
import [COMPONENTNAME]Base from './[COMPONENTNAME]Base';
`const [COMPONENTNAME] = styled( [COMPONENTNAME]

There are two mentions of a reactide.config.js file in the README:

The component tree works out-of-the-box by finding the entry point to your React application that you provide inside the reactide.config.js file.

Go to the reactide.config.js file and change the .html and .js entry points to the relative path of your respective files.

But I could not find any examples or documentation

I'm evaluating SuperTest for use as an end-to-end testing framework for an API implemented in PHP. So I need to run the tests via actual HTTP against some configurable base URL. After a lot of poking around, I found that I can just pass that base URL to the module's constructor, as in

request( 'http://localhost:8080/dummy/' ).get('api.php')

This is undocumented though, and even violates t

Context

A developer might attempt to do:

interface NoIndexSignature {
  a: 'a';
}

const matcher: NoIndexSignature = { a: 'a' };

nock('https://example.com').put('/', matcher);

which will not pass the type checking as opposed to

const matcher: { a: 'a' } = { a: 'a' };

nock('https://example.com').put('/', matcher);

I think this might be by design,

Packages:
@apollo/federation: 0.11.2
apollo-server-express: 2.9.9

The documenation leads me to believe that setting these options { engine: true, reporting: false } in the server constructor should disable reporting for a federated service (so that the gateway can do that work.) When I do this though I am

Hi, if you are reading this is because you pretty likely don't know how to start 🤔 . Fair enough !

So, let's fix that 🚸 !

What should I know before start?

All here we are developers with different backgrounds, languages and objectives. But, all we must follow certain rules so we can understand each other and make the communication easier as possible. Please 👍 read your [code of conduc

This is wrong and needs some updates. exclude, specs, maxInstances, shardTestFiles, count, seleniumAddress are not capabilities.

https://github.com/angular/protractor/blob/master/lib/config.ts#L300-L322

Please submit PR's to the selenium4 branch.

Related: angular/protractor#5128

I am trying to run an express app through Visual Studio Code. I have a launch.json file with DEBUG defined like so:

        "env": {
             "DEBUG": "*"
        }

Here is a trimmed down version of my app.js file where you can see the bolded debug line that doesn't output to the debug console (Test 2). Test 1 before it outputs as expected. If I run this from the command li

AWS Lambda currently supports Node v10.x
Can you please support it.

When using git cz, one option for a type to select is "improvement", but this fails the enum check

husky > commit-msg hook failed (add --no-verify to bypass)
git exited with error code 1
kris@Kriss-MacBook-Pro cent-admin % git cz
cz-cli@4.0.3, cz-conventional-changelog@3.0.1

? Select the type of change that you're committing: 
  revert:      Reverts a previous commit 
  feat:

From cTheDragons:

It appears the username in the settings on the web has not been updated since the changeover. It states:
"We will be transitioning login names to unique, public usernames soon. This username will be used for invitations, @mentions in chat, and messaging."

From shanaqui:
![image](https://user-images.githubusercontent.com/1495809/51815458-cd275f00-230c-11e9-8f95-457e57bc7c7