Describe your problem and how to reproduce it:
This passes:

let favRegex = /favou?rite/i;

But this doesn't:

let favRegex = /favou?rite/gi;

with the error message:

// running tests
Your regex shoul

Section/Content To Improve
Section "Config order of precedence".

Suggested Improvement
The current implementation of

• Version: v10.x
• Platform: all
• Subsystem: repl

What steps will reproduce the bug?

$ node
> function foo() {
... let n = 10n;
Thrown:
let n = 10n;
           ^

SyntaxError: Unexpected end of input
>

How often does it reproduce? Is there a required condition?

Reproduces all the time.

What is the expected behavior?

Should not cause an

Express uses hardcoded values for debug namespace, for example:
https://github.com/expressjs/express/blob/b69b7605b07b41273acc931d25ab585377bcd107/lib/router/index.js#L20

and it is extremly hard to determine in output where things are happening while doing TDD on microservices architecture. It would be nice to allow to specify prefix for namespace, i.e. per microservice which is an express app.

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

Some of the issues below are already mentioned in other tickets, but I have the feeling that a proper generic issue is due to give it visibility, as for now the current package is unusable for many users.

1. The typescript package doesn't respect the tsconfig flags, and many of them are hardcoded inside the meteor/babel package.
   I understand that meteor needs to control some compilation option

Minor thing, but would be nice to be able to get to dev tools without right click + Inspect, especially when menu is shown by the app on right click.

NWJS Version : 0.45.1
Operating System : macOS Catalina

Expected behavior

Devtools menu item or command + option + I should open dev tools

Actual behavior

It works in nw1 mode, but not in nw2, has been like that for a whil

Issue Summary

Bookmark card has few minor issues atm as listed below -

• Better error message handling: Currently bookmark card fails with Unable to parse URL error in case of all failures including insufficient metadata available. We should differentiate between "unable to parse" and "page has insufficient metadata" cases and show appropriate error message to avoid confusion (ref: ht

There is no "pre-deploy" hook listed here as an option at https://pm2.keymetrics.io/docs/usage/deployment/. It should also be mentioned that this hook will run BEFORE git pull occurs, e.g. you may want to suggest to users to put git reset --hard as the pre-deploy hook in case their files such as yarn.lock change frequently, or localization occurs.

Check List

Please check followings before submitting a new feature request.

• I have already read Docs page
• I have already searched existing issues

Feature Request

New to Hexo and finding some inadequacies in some of the documentation.

• Under Helpers List Tags (and other list_ helpers) the "style"

We have some documentation about using IBM Watson: https://github.com/sahat/hackathon-starter#ibm-watson

It would be great if we have one or more working API examples using Watson or ML/AI APIs that are provided by other companies such as Microsoft or AWS.

Describe the bug
Find-one endpoint /resource/:id responses with 500 status code instead of 404, this happens with MongoDB setup.

Steps to reproduce the behavior

1. Setup Strapi with MongoDB configuration.
2. Create a collection (resource).
3. Give findOne access to the public.
4. Send a request to /resource-name/any-invalid-id.

Expected behavior
404 response.

**Sys

https://eslint.org/docs/rules/use-isnan

This is a proposal to modify the use-isnan rule.

Current rule setting:

use-isnan: "error"

Proposed rule setting:

["error", {"enforceForSwitchCase": true}]

The switch statement internally uses the === comparison to match the expression's value to a case clause.
Therefore, it can never match _case NaN. Also, `swit

parseISO v2 documentation currently states

The previous parse implementation was renamed to parseISO.

parse v2 documentation currently states

Old parse was renamed to toDate. Now parse is a new function which parses a string using a provided format.

I think considering the sentence is to divert people who have previously been using v1 parse to the correct v2 equivalent, it only

This issue (webtorrent/webtorrent#1685) mentioned a nice resource that shows how to integrate WebTorrent with various JS video libraries.

https://qiita.com/mehdi/items/22ba55ae30bdcedd0746

Would be nice to add updated versions of these examples to the docs.

const XLSX = require('xlsx');

const wb = XLSX.utils.book_new();

const ws = XLSX.utils.json_to_sheet([]);

XLSX.utils.book_append_sheet(wb, ws, 'Bug sheet');

ws.A1 = { t: 's', f: 'square' };

XLSX.writeFile(wb, 'formula.ods');

The resulting .ODS file contains:

<table:table-cell table:formula="of:=square" office:value-type="string"><text:p>undefined</text:p></table

Too wide (and falsy) segregation of GraphQL Types and Resolvers

The first example of this is new ObjectType in src/data/queries/index.js importing fields.
Fields should be taken in context of parent type, not as standalone information.

This can ensure some users that custom types cannot have own field resolvers which is false.

In fact, much of fields which can have own resolvers

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

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

Is your feature request related to a problem? Please describe.
Deployed Parse server using k8 and used /parse/health for the readinessProbe and livenessProbe probe. But when deploy new code and broke the database connection, /parse/health still returns 200 OK. So old container was killed and new broken one brought online

Describe the solution you'd like
Only return 200 ok after db is

When using a dark theme, the menu bar stays white:

Instead the app should check the current theme and if it's a dark one, the menu bar should be made black (assuming Electron supports this).

Hello, could we somehow document #522 / provide a better error message? I've spent waaaaay too much time trying to solve the issue before finding the already existing solution:/

Even better - fix it, instead of a work-around?

Thanks!

具体报错如下图

F:\github\myStudy\node\lesson6>mocha

test/main.test.js
1) should equal 0 when n === 0
2) should equal 1 when n === 1
3) should equal 55 when n === 10
√ should throw when n > 10
√ should throw when n < 0
√ should throw when is not Number

3 passing (35ms)
3 failing

1. test/main.test.js should equal 0 when n === 0:
   AssertionError: e

there are two configs in the project.

egg-sequelize use the config.default.js.

sequelize:init generate config.json.

it is not clear.

i like use the sequelize-cli to generate model. so can I not use the egg-sequelize?

I am making a health check endpoint for kubernetes (google cloud's service to host containerized applications) for my mySql application.

right now I am using this package https://www.npmjs.com/package/health-check-mysql

But is there something built into the package itself, something like a isConnected method. ie:
connection.isConnected() ? throw new Error('not connected to mysql') : null

With log: {backend: "stdout", level: "..."} in config.js the daemon ignores the log level and still prints everything to stdout. This seems to be the result of lib/logger.js using util.log (deprecated since 6.0.0 20 months ago) which does not support log levels.

If the stdout logger cannot be easily made to respect the log level, it would be helpful if the config documentation in `exam