Bumps mocha from 7.2.0 to 8.2.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/mochajs/mocha/releases">mocha's releases</a>.</em></p> <blockquote> <h2>v8.2.0</h2> <h1>8.2.0 / 2020-10-16</h1> <p>The major feature added in v8.2.0 is addition of support for <a href="https://mochajs.org/#global-fixtures"><em>global fixtures</em></a>.</p> <p>While Mocha has always had the ability to run setup and teardown via a hook (e.g., a <code>before()</code> at the top level of a test file) when running tests in serial, Mocha v8.0.0 added support for parallel runs. Parallel runs are <em>incompatible</em> with this strategy; e.g., a top-level <code>before()</code> would only run for the file in which it was defined.</p> <p>With <a href="https://mochajs.org/#global-fixtures">global fixtures</a>, Mocha can now perform user-defined setup and teardown <em>regardless</em> of mode, and these fixtures are guaranteed to run <em>once and only once</em>. This holds for parallel mode, serial mode, and even "watch" mode (the teardown will run once you hit Ctrl-C, just before Mocha finally exits). Tasks such as starting and stopping servers are well-suited to global fixtures, but not sharing resources--global fixtures do <em>not</em> share context with your test files (but they do share context with each other).</p> <p>Here's a short example of usage:</p> <pre lang="js"><code>// fixtures.js <p>// can be async or not exports.mochaGlobalSetup = async function() { this.server = await startSomeServer({port: process.env.TEST_PORT}); console.log(<code>server running on port ${this.server.port}</code>); };</p> <p>exports.mochaGlobalTeardown = async function() { // the context (<code>this</code>) is shared, but not with the test files await this.server.stop(); console.log(<code>server on port ${this.server.port} stopped</code>); };</p> <p>// this file can contain root hook plugins as well! // exports.mochaHooks = { ... } </code></pre></p> <p>Fixtures are loaded with <code>--require</code>, e.g., <code>mocha --require fixtures.js</code>.</p> <p>For detailed information, please see the <a href="https://mochajs.org/#global-fixtures">documentation</a> and this handy-dandy <a href="https://mochajs.org/#test-fixture-decision-tree-wizard-thing">flowchart</a> to help understand the differences between hooks, root hook plugins, and global fixtures (and when you should use each).</p> <h2>:tada: Enhancements</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4308">#4308</a>: Support run-once <a href="https://mochajs.org/#global-fixtures">global setup & teardown fixtures</a> (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4442">#4442</a>: Multi-part extensions (e.g., <code>test.js</code>) now usable with <code>--extension</code> option (<a href="https://github.com/jordanstephens"><strong>@jordanstephens</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4472">#4472</a>: Leading dots (e.g., <code>.js</code>, <code>.test.js</code>) now usable with <code>--extension</code> option (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4434">#4434</a>: Output of <code>json</code> reporter now contains <code>speed</code> ("fast"/"medium"/"slow") property (<a href="https://github.com/wwhurin"><strong>@wwhurin</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4464">#4464</a>: Errors thrown by serializer in parallel mode now have error codes (<a href="https://github.com/evaline-ju"><strong>@evaline-ju</strong></a>)</li> </ul> <p><em>For implementors of custom reporters:</em></p> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4409">#4409</a>: Parallel mode and custom reporter improvements (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>): <ul> <li>Support custom worker-process-only reporters (<code>Runner.prototype.workerReporter()</code>); reporters should subclass <code>ParallelBufferedReporter</code> in <code>mocha/lib/nodejs/reporters/parallel-buffered</code></li> <li>Allow opt-in of object reference matching for "sufficiently advanced" custom reporters (<code>Runner.prototype.linkPartialObjects()</code>); use if strict object equality is needed when consuming <code>Runner</code> event data</li> <li>Enable detection of parallel mode (<code>Runner.prototype.isParallelMode()</code>)</li> </ul> </li> </ul> <h2>:bug: Fixes</h2> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/mochajs/mocha/blob/master/CHANGELOG.md">mocha's changelog</a>.</em></p> <blockquote> <h1>8.2.0 / 2020-10-16</h1> <p>The major feature added in v8.2.0 is addition of support for <a href="https://mochajs.org/#global-fixtures"><em>global fixtures</em></a>.</p> <p>While Mocha has always had the ability to run setup and teardown via a hook (e.g., a <code>before()</code> at the top level of a test file) when running tests in serial, Mocha v8.0.0 added support for parallel runs. Parallel runs are <em>incompatible</em> with this strategy; e.g., a top-level <code>before()</code> would only run for the file in which it was defined.</p> <p>With <a href="https://mochajs.org/#global-fixtures">global fixtures</a>, Mocha can now perform user-defined setup and teardown <em>regardless</em> of mode, and these fixtures are guaranteed to run <em>once and only once</em>. This holds for parallel mode, serial mode, and even "watch" mode (the teardown will run once you hit Ctrl-C, just before Mocha finally exits). Tasks such as starting and stopping servers are well-suited to global fixtures, but not sharing resources--global fixtures do <em>not</em> share context with your test files (but they do share context with each other).</p> <p>Here's a short example of usage:</p> <pre lang="js"><code>// fixtures.js <p>// can be async or not exports.mochaGlobalSetup = async function() { this.server = await startSomeServer({port: process.env.TEST_PORT}); console.log(<code>server running on port ${this.server.port}</code>); };</p> <p>exports.mochaGlobalTeardown = async function() { // the context (<code>this</code>) is shared, but not with the test files await this.server.stop(); console.log(<code>server on port ${this.server.port} stopped</code>); };</p> <p>// this file can contain root hook plugins as well! // exports.mochaHooks = { ... } </code></pre></p> <p>Fixtures are loaded with <code>--require</code>, e.g., <code>mocha --require fixtures.js</code>.</p> <p>For detailed information, please see the <a href="https://mochajs.org/#global-fixtures">documentation</a> and this handy-dandy <a href="https://mochajs.org/#test-fixture-decision-tree-wizard-thing">flowchart</a> to help understand the differences between hooks, root hook plugins, and global fixtures (and when you should use each).</p> <h2>:tada: Enhancements</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4308">#4308</a>: Support run-once <a href="https://mochajs.org/#global-fixtures">global setup & teardown fixtures</a> (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4442">#4442</a>: Multi-part extensions (e.g., <code>test.js</code>) now usable with <code>--extension</code> option (<a href="https://github.com/jordanstephens"><strong>@jordanstephens</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4472">#4472</a>: Leading dots (e.g., <code>.js</code>, <code>.test.js</code>) now usable with <code>--extension</code> option (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4434">#4434</a>: Output of <code>json</code> reporter now contains <code>speed</code> ("fast"/"medium"/"slow") property (<a href="https://github.com/wwhurin"><strong>@wwhurin</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4464">#4464</a>: Errors thrown by serializer in parallel mode now have error codes (<a href="https://github.com/evaline-ju"><strong>@evaline-ju</strong></a>)</li> </ul> <p><em>For implementors of custom reporters:</em></p> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4409">#4409</a>: Parallel mode and custom reporter improvements (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>): <ul> <li>Support custom worker-process-only reporters (<code>Runner.prototype.workerReporter()</code>); reporters should subclass <code>ParallelBufferedReporter</code> in <code>mocha/lib/nodejs/reporters/parallel-buffered</code></li> <li>Allow opt-in of object reference matching for "sufficiently advanced" custom reporters (<code>Runner.prototype.linkPartialObjects()</code>); use if strict object equality is needed when consuming <code>Runner</code> event data</li> <li>Enable detection of parallel mode (<code>Runner.prototype.isParallelMode()</code>)</li> </ul> </li> </ul> <h2>:bug: Fixes</h2> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/mochajs/mocha/commit/afe8daac603d398743dd5572f497ba088193bf53"><code>afe8daa</code></a> Release v8.2.0</li> <li><a href="https://github.com/mochajs/mocha/commit/20d3d4cab80d65096fbb15eb5eaf14abdcc587dd"><code>20d3d4c</code></a> update CHANGELOG for v8.2.0 [ci skip]</li> <li><a href="https://github.com/mochajs/mocha/commit/932c09a607040e9aaee11a4dc2a5397831574c0c"><code>932c09a</code></a> fix scripts/linkify-changelog to not blast fenced code blocks</li> <li><a href="https://github.com/mochajs/mocha/commit/3b333ecf6168943605caa1bcd07b2acf38835057"><code>3b333ec</code></a> chore(deps): [email protected]</li> <li><a href="https://github.com/mochajs/mocha/commit/058b2e7484f0040e5ff0b4d2e37bf41f2cf50da3"><code>058b2e7</code></a> attempt to force colors in karma config</li> <li><a href="https://github.com/mochajs/mocha/commit/60e3662511dcdaa0b854909b866841191a32771a"><code>60e3662</code></a> replace promise.allsettled with @ungap/promise-all-settled; closes <a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4474">#4474</a></li> <li><a href="https://github.com/mochajs/mocha/commit/f132448ee51d9b09efab29099756f3b15a1a98ba"><code>f132448</code></a> remove duplicated/problem reporter tests; closes <a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4469">#4469</a></li> <li><a href="https://github.com/mochajs/mocha/commit/31116dbf825487490d5416c95b2685e18e7359d3"><code>31116db</code></a> fix: remove job count from parallel mode debug log (<a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4416">#4416</a>)</li> <li><a href="https://github.com/mochajs/mocha/commit/478ca6ac3d05d7d789d3ec22328b3a2ce859e341"><code>478ca6a</code></a> add "fixture flowchart" to docs (<a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4440">#4440</a>)</li> <li><a href="https://github.com/mochajs/mocha/commit/9c28990f1d562aff3ceb410496c46266099a9d5f"><code>9c28990</code></a> support leading dots in --extension</li> <li>Additional commits viewable in <a href="https://github.com/mochajs/mocha/compare/v7.2.0...v8.2.0">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>

@dependabot ignore this dependency

I've created a tiny, self-contained secp256k1 in typescript. It's faster than other js deps.

It would be great if it was used here. Seems to match the purpose

https://github.com/paulmillr/noble-secp256k1

Check out the blog post:

https://paulmillr.com/posts/noble-secp256k1-fast-ecc/

That's what makes deep packet inspection much more useful afaik. Sad!

there's encrypted SNI though, a part of tls 1.3

Using the readme example the below does not verify using node v 12.0.

        const msg = 'hello';
        const privateKeys = [
            '18f020b98eb798752a50ed0563b079c125b0db5dd0b1060d1c1b47d4a193e1e4',
            'ed69a8c50cf8c9836be3b67c7eeff416612d45ba39a5c099d48fa668bf558c9c',
            '16ae669f3be7a2121e17d0c68c05a8f3d6bef21ec0f2315f1d7aec12484e4cf5'
        ];
        const publicKeys = privateKeys.map(bls.getPublicKey);
        const signatures = await Promise.all(privateKeys.map(p => bls.sign(msg, p)));
        const aggPubKey: any  = await bls.aggregatePublicKeys(publicKeys);
        const aggSignature = await bls.aggregateSignatures(signatures);
        const isCorrect = await bls.verify(aggSignature, msg, aggPubKey);

      //=> returns false
      console.log({isCorrect});

update the package, fixed in 0.6

Can you shed some light on it? How does a packet with alpn look like? Is it always used by webservers?

Seems like alpn is not deployed widely yet?

Main yarn.lock mentions chokidar@^2.0.0, chokidar@*, [email protected], [email protected].

Is there a reason vscode uses several different versions of chokidar & readdirp?

Big Sur allows to use encrypted DNS. This is very useful for privacy. See: https://paulmillr.com/posts/encrypted-dns/

Perhaps it would make sense to include some eDNS advice in the guide.

[email protected] is out now.

@dependabot ignore this major version

Bumps mocha from 7.2.0 to 8.1.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/mochajs/mocha/releases">mocha's releases</a>.</em></p> <blockquote> <h2>v8.1.3</h2> <h1>8.1.3 / 2020-08-28</h1> <h2>:bug: Fixes</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4425">#4425</a>: Restore <code>Mocha.utils.lookupFiles()</code> and Webpack compatibility (both broken since v8.1.0); <code>Mocha.utils.lookupFiles()</code> is now <strong>deprecated</strong> and will be removed in the next major revision of Mocha; use <code>require('mocha/lib/cli').lookupFiles</code> instead (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> </ul> <h2>v8.1.2</h2> <h1>8.1.2 / 2020-08-25</h1> <h2>:bug: Fixes</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4418">#4418</a>: Fix command-line flag incompatibility in forthcoming Node.js v14.9.0 (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4401">#4401</a>: Fix missing global variable in browser (<a href="https://github.com/irrationelle"><strong>@irrationelle</strong></a>)</li> </ul> <h2>:lock: Security Fixes</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4396">#4396</a>: Update many dependencies (<a href="https://github.com/GChuf"><strong>@GChuf</strong></a>)</li> </ul> <h2>:book: Documentation</h2> <ul> <li>Various fixes by <a href="https://github.com/sujin-park"><strong>@sujin-park</strong></a>, <a href="https://github.com/wwhurin"><strong>@wwhurin</strong></a> & <a href="https://github.com/Donghoon759"><strong>@Donghoon759</strong></a></li> </ul> <h2>v8.1.1</h2> <h1>8.1.1 / 2020-08-04</h1> <h2>:bug: Fixes</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4394">#4394</a>: Fix regression wherein certain reporters did not correctly detect terminal width (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> </ul> <h2>v8.1.0</h2> <h1>8.1.0 / 2020-07-30</h1> <p>In this release, Mocha now builds its browser bundle with Rollup and Babel, which will provide the project's codebase more flexibility and consistency.</p> <p>While we've been diligent about backwards compatibility, it's <em>possible</em> consumers of the browser bundle will encounter differences (other than an increase in the bundle size). If you <em>do</em> encounter an issue with the build, please <a href="https://github.com/mochajs/mocha/issues/new?labels=unconfirmed-bug&template=bug_report.md&title=">report it here</a>.</p> <p>This release <strong>does not</strong> drop support for IE11.</p> <p>Other community contributions came from <a href="https://github.com/Devjeel"><strong>@Devjeel</strong></a>, <a href="https://github.com/Harsha509"><strong>@Harsha509</strong></a> and <a href="https://github.com/sharath2106"><strong>@sharath2106</strong></a>. <em>Thank you</em> to everyone who contributed to this release!</p> <blockquote> <p>Do you read Korean? See <a href="https://blog.outsider.ne.kr/1489">this guide to running parallel tests in Mocha</a>, translated by our maintainer, <a href="https://github.com/outsideris"><strong>@outsideris</strong></a>.</p> </blockquote> <h2>:tada: Enhancements</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4287">#4287</a>: Use background colors with inline diffs for better visual distinction (<a href="https://github.com/michael-brade"><strong>@michael-brade</strong></a>)</li> </ul> <h2>:bug: Fixes</h2> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/mochajs/mocha/blob/master/CHANGELOG.md">mocha's changelog</a>.</em></p> <blockquote> <h1>8.1.3 / 2020-08-28</h1> <h2>:bug: Fixes</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4425">#4425</a>: Restore <code>Mocha.utils.lookupFiles()</code> and Webpack compatibility (both broken since v8.1.0); <code>Mocha.utils.lookupFiles()</code> is now <strong>deprecated</strong> and will be removed in the next major revision of Mocha; use <code>require('mocha/lib/cli').lookupFiles</code> instead (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> </ul> <h1>8.1.2 / 2020-08-25</h1> <h2>:bug: Fixes</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4418">#4418</a>: Fix command-line flag incompatibility in forthcoming Node.js v14.9.0 (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4401">#4401</a>: Fix missing global variable in browser (<a href="https://github.com/irrationelle"><strong>@irrationelle</strong></a>)</li> </ul> <h2>:lock: Security Fixes</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4396">#4396</a>: Update many dependencies (<a href="https://github.com/GChuf"><strong>@GChuf</strong></a>)</li> </ul> <h2>:book: Documentation</h2> <ul> <li>Various fixes by <a href="https://github.com/sujin-park"><strong>@sujin-park</strong></a>, <a href="https://github.com/wwhurin"><strong>@wwhurin</strong></a> & <a href="https://github.com/Donghoon759"><strong>@Donghoon759</strong></a></li> </ul> <h1>8.1.1 / 2020-08-04</h1> <h2>:bug: Fixes</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4394">#4394</a>: Fix regression wherein certain reporters did not correctly detect terminal width (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> </ul> <h1>8.1.0 / 2020-07-30</h1> <p>In this release, Mocha now builds its browser bundle with Rollup and Babel, which will provide the project's codebase more flexibility and consistency.</p> <p>While we've been diligent about backwards compatibility, it's <em>possible</em> consumers of the browser bundle will encounter differences (other than an increase in the bundle size). If you <em>do</em> encounter an issue with the build, please <a href="https://github.com/mochajs/mocha/issues/new?labels=unconfirmed-bug&template=bug_report.md&title=">report it here</a>.</p> <p>This release <strong>does not</strong> drop support for IE11.</p> <p>Other community contributions came from <a href="https://github.com/Devjeel"><strong>@Devjeel</strong></a>, <a href="https://github.com/Harsha509"><strong>@Harsha509</strong></a> and <a href="https://github.com/sharath2106"><strong>@sharath2106</strong></a>. <em>Thank you</em> to everyone who contributed to this release!</p> <blockquote> <p>Do you read Korean? See <a href="https://blog.outsider.ne.kr/1489">this guide to running parallel tests in Mocha</a>, translated by our maintainer, <a href="https://github.com/outsideris"><strong>@outsideris</strong></a>.</p> </blockquote> <h2>:tada: Enhancements</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4287">#4287</a>: Use background colors with inline diffs for better visual distinction (<a href="https://github.com/michael-brade"><strong>@michael-brade</strong></a>)</li> </ul> <h2>:bug: Fixes</h2> <ul> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4328">#4328</a>: Fix "watch" mode when Mocha run in parallel (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4382">#4382</a>: Fix root hook execution in "watch" mode (<a href="https://github.com/indieisaconcept"><strong>@indieisaconcept</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4383">#4383</a>: Consistent auto-generated hook titles (<a href="https://github.com/cspotcode"><strong>@cspotcode</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4359">#4359</a>: Better errors when running <code>mocha init</code> (<a href="https://github.com/boneskull"><strong>@boneskull</strong></a>)</li> <li><a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4341">#4341</a>: Fix weirdness when using <code>delay</code> option in browser (<a href="https://github.com/craigtaub"><strong>@craigtaub</strong></a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/mochajs/mocha/commit/fa9e67c6ba2e2af6f7cc70e51b2c97db94c73ad0"><code>fa9e67c</code></a> Release v8.1.3</li> <li><a href="https://github.com/mochajs/mocha/commit/b1729c68a0be8308434a4f89fd2e25217d54a635"><code>b1729c6</code></a> update CHANGELOG.md for v8.1.3 [skip ci]</li> <li><a href="https://github.com/mochajs/mocha/commit/051f9f61065ccb5b5960de22cd59a7e8b42123ad"><code>051f9f6</code></a> assert mocha is bundle-able by webpack; fixes <a href="https://github-redirect.dependabot.com/mochajs/mocha/issues/4422">#4422</a></li> <li><a href="https://github.com/mochajs/mocha/commit/52f07f01894504615cd412c91cfad8e9b8a6d76e"><code>52f07f0</code></a> restore and deprecate lookupFiles() in lib/utils</li> <li><a href="https://github.com/mochajs/mocha/commit/247d9611ea1a77d1c1029b0eae812b271445592f"><code>247d961</code></a> alias lookupFiles, loadRc, loadPkgRc and loadOptions to lib/cli module; fixes...</li> <li><a href="https://github.com/mochajs/mocha/commit/4b2b6e06c58c9580333edd9cb0e67128641ba99f"><code>4b2b6e0</code></a> update @mocha/docdash to latest version</li> <li><a href="https://github.com/mochajs/mocha/commit/4976e179774aea28bc788c6e237330ce932d218d"><code>4976e17</code></a> refactor assertions into an actual unexpected plugin</li> <li><a href="https://github.com/mochajs/mocha/commit/8bc376cb4d4049740e5882a830411aa86b2265b6"><code>8bc376c</code></a> fix lintstagedrc</li> <li><a href="https://github.com/mochajs/mocha/commit/c733254a5c28504e9fcd2e2954b580980c4583dd"><code>c733254</code></a> Release v8.1.2</li> <li><a href="https://github.com/mochajs/mocha/commit/5f69c286a2ddcb00adfe41feda7402f42292a999"><code>5f69c28</code></a> update changelog for v8.1.2 [skip ci]</li> <li>Additional commits viewable in <a href="https://github.com/mochajs/mocha/compare/v7.2.0...v8.1.3">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

</details>

@bpasero have you had a chance to test this on win32?

Is there any way to test this with readdirp@master? This should handle it.

I'll try to dig into this today, if I can't, i'll look around pushing a temp option that disables the behavior

@bpasero I don't think we can easily handle cases like this, can we?

@bpasero in your tests, CPU usage became smaller, but from reports, it got up?

@AubreyHewes 9.3.5-canary is very different from 9.3.4. Like, "a new release" different. Naming it 9.3.5 feels like it's a simple patch-version bugfix.

Alright. Does this mean we could close the issue?

Thanks for auditing the code.

powMod is unsafe, because it's used in fromRistrettoBytes, which decodes a byte-string s_bytes representing a compressed Ristretto point into extended coordinates. It's basically a conversion.

It is different from fromRistrettoHash, which applies Elligator twice.

Now, the question here is: do we need constant-timeness in fromRistrettoBytes?

As an optimization, i'm already using multiplyUnsafe in verify(). The reason for this is that verify doesn't work with private data, and speed gains from it are massive, like 1.5-2x.

Thank you!

It could be an option to pass as parameter, a "plugin" of some sort, or maybe even a new related tool (in other repository). Please let me know if this is of your interest, if have tried in the past, if you think there are good reasons not do so, etc.

With AST option on, small unmeaningful changes wouldn't trigger change event (";", spaces, changing variable names in some cases). This could be even put together with minification (which would ignore variable names, imports, filenames imported, etc), all with performance impacts for sure.

Since this lib is used by a lot of other tools, this could get pretty handy. E.g.: watch that causes to reload servers. It will reload only if "compiled" code is different. PS: rollup uses this logic internally.

I can do a PR with some guidance, if this proposal is accepted

That's out of scope for my Chokidar vision — sorry. Feel free to fork the project to your needs.

This line:

https://github.com/paulmillr/encrypted-dns/blob/master/cloudflare-https.mobileconfig#L23

... should probably say Configures device to use Cloudflare Encrypted DNS over HTTPS, not TLS.

https://gcd.cr.yp.to

https://github.com/fmoreira-icpc/safegcd/blob/6ce34e4b1ed1574986915b09f101239b5316428a/gcd.c#L102-L131

I spend the whole night trying to solve this issue!!!!!! And still unable to fix it.. Any thoughts???

node-pre-gyp WARN Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.4/fse-v1.2.4-node-v72-darwin-x64.tar.gz node-pre-gyp WARN Pre-built binaries not found for [email protected] and [email protected] (node-v72 ABI, unknown) (falling back to source compile with node-gyp)

Make your dependencies upgrade to fsevents v2-latest, fsevents v1 with gyp is unsupported.

US7995752B2/US7110538B2 got expired

US7995752B2 got expired

Primary DNS: 1.1.1.2 Secondary DNS: 1.0.0.2 https://security.cloudflare-dns.com/dns-query

We don't need "signed" profiles. This repo only contains unsigned ones.

Signed profiles cannot be audited easily.

Seems like something is wrong with AdGuard. The files are "binary" and 5kb. Others files in the repo including dnspod are 1kb.

Hello author, I would like to ask how to get the signature, I also want to get DNS, purr purr.

Just adjust the profile config file to your needs. Change IPs and server url. The files are in text format.

The encrypted api is public & official.

Thanks!

Feel free to submit a pull request.

Which signature?

The idea is simple. Switch to Uint8Arrays, which would allow the library to be used in browsers without deps. Which would potentially increase its usage.

If you don't want to maintain it, just keep using the old version. It's time to more forward with the progress here.

so trying to find time to take on this task is difficult

Not really, it's just a question of priorities. I have very popular packages that require much more maintenance, and I have a bunch of businesses to run, and life outside the internet etc. Still finding time to work on stuff like this.

affects tons of libraries that rely on this

If you follow semver and bump a major version, the users would not be affected.

I do want to move forward with this

That seems like a "your call is important for us" I receive when I call bank's support & wait for 20 minutes.

Create a fork package

I did this the second I published the rewrite. After that, decided to pull it back, because i've thought you're going to merge it in a couple days. The goal here is to let all bech32 users benefit from the change.

@lukechilds ping?

That seems really simple.

Describe the bug

I am trying to run Storybook 6 on Windows 10 and I get this error. Storybook is unable to run. On WSL2 and Docker under the exact same code, everything works fine.

The following error pops up:

Error from chokidar (C:\): Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp'
Error from chokidar (C:\): Error: EBUSY: resource busy or locked, lstat 'C:\hiberfil.sys'
Error from chokidar (C:\): Error: EBUSY: resource busy or locked, lstat 'C:\pagefile.sys'
Error from chokidar (C:\): Error: EBUSY: resource busy or locked, lstat 'C:\swapfile.sys'

Versions (please complete the following information):

• Chokidar version 3.4.1
• Node version v10.15.0, v12 and v14.11.0
• OS version: Windows 10

To Reproduce:

Try to run a storybook 6 project.

Expected behavior Should launch.

you're watching swapfile and hibernation files. The error is legit. You should not be watching them. Watch something more granular e.g. C:\Files\dir, not C:\

Hi @lrvick

Just wanted to mention that there's a tool called Rollup (https://rollupjs.org/) which allows to create single JS files from tons of npm (etc) dependencies.

It's very useful and configurable. You can compile separate files from a node/browser, and you can compile code that works in both cases — even though browsers don't support common.js modules from node

try { 3 | module.exports = require("chokidar"); {

4 | return; | ^ 5 | } 6 | } catch(e) { 7 | v3Err = e; at Object._raise (E:\test\node_modules@babel\parser\src\parser\error.js:60:45) at Object.raiseWithData (E:\test\node_modules@babel\parser\src\parser\error.js:55:17) at Object.raise (E:\test\node_modules@babel\parser\src\parser\error.js:39:17) at Object.parseReturnStatement (E:\test\node_modules@babel\parser\src\parser\statement.js:563:12) at Object.parseStatementContent (E:\test\node_modules@babel\parser\src\parser\statement.js:197:21) at Object.parseStatement (E:\test\node_modules@babel\parser\src\parser\statement.js:151:17) at Object.parseBlockOrModuleBlockBody (E:\test\node_modules@babel\parser\src\parser\statement.js:873:25) at Object.parseBlockBody (E:\test\node_modules@babel\parser\src\parser\statement.js:843:10) at Object.parseBlock (E:\test\node_modules@babel\parser\src\parser\statement.js:813:10) at Object.parseStatementContent (E:\test\node_modules@babel\parser\src\parser\statement.js:218:21) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] start: pawjs --no-cache --config=./pawconfig.json --env=development start npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\name\AppData\Roaming\npm-cache_logs\2020-08-17T09_19_41_742Z-debug.log

@pipobscure could you push out a new v1 release, please?

@pipobscure should we port this to 2.x?

thanjks

Initialize async member otherwise it may happen that in FSEvents::asyncStart() the check async.data == this is already true and as a result uv_async_init() is not called.

Refs.: https://github.com/nodejs/node/pull/34776#issuecomment-674314154

With so many issues that people create about the EBADPLATFORM issue on non-Mac systems, why is this info not in the README?